You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, the wildcard variable in the test is handled inconsistently between the library bundle format and the AMD module format. The CFE now renames wildcards to temporary variables as multiple wildcards can exist.
Library bundle format: Correctly excludes the wildcard variable from debugging.
AMD module format: Emits _ instead of a temporary name.
Per the discussion with DDC folks, it was agreed that wildcard variables are not expected to be available via debugging. Therefore, the library bundle format's behavior is correct, while the AMD format's behavior might not be.
The text was updated successfully, but these errors were encountered:
might is a good qualifier. It's undefined behavior on what a wildcard's JS name should be. Because of that, _ is a totally valid JS name as long as it doesn't conflict, but it'll require a bit more testing to determine if it's doing something erroneous.
Description:
Currently, the wildcard variable in the test is handled inconsistently between the library bundle format and the AMD module format. The CFE now renames wildcards to temporary variables as multiple wildcards can exist.
Library bundle format: Correctly excludes the wildcard variable from debugging.
AMD module format: Emits
_
instead of a temporary name.Per the discussion with DDC folks, it was agreed that wildcard variables are not expected to be available via debugging. Therefore, the library bundle format's behavior is correct, while the AMD format's behavior might not be.
The text was updated successfully, but these errors were encountered: