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.
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 notstring(exportName extends Name).These all work the same as commands, tasks, and subscriptions.
For:
Before change:
After change: