fix: all resources have name type param

[thantos]

No description provided.

[sam-goodwin]

Do we need it on workflow? Does it have a representation on the cdk side? Maybe monitoring?

[thantos]

I think we should be consistent. A workflow may be addressable if it supported overrides to the destination of task, injection of env variables, permission to invoke it, or analytics.

[thantos]

Same argument for transactions

Forgot something

[sam-goodwin]

I don't see the changes to the way we extract the types on the cdk side? Is it still using the export name instead of the string literal? We have code to check if the export name is the same as the string name and favor it to maintain the ide connection when it's the same.

[thantos]

They were all using the types with logic to check for "same as export name" and "different from export name".

When the Resource["name"] resolved to a string, it is always considered to be the same as the export name. (exportName extends string). Now that a type parameter is used for name in the interfaces/specs, the export name is compared to the string literal type and not string (exportName extends Name).

These all work the same as commands, tasks, and subscriptions.

For:

Before change:

After change: