Update wildcard handling in tests for proper debugging behavior
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 2
Description
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.
Contributor guide
Research direction
Locate the wildcard-handling tests for the library bundle and AMD module formats, then trace how the CFE renames wildcard variables and how debugging output is asserted. Compare the two formats against the discussion's agreed debugging behavior. Done means the tests consistently capture the intended treatment of wildcard variables and clarify the AMD discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100