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
Map scopes transforms build/compressed into how the original source behaves. It's magical when enabled buy we can't enable it by default as it has performance overhead (especially on the first pause).
It makes several variable-related features more reliable:
Scopes pane
Variable hover preview (without it preview will not work at all for original variables)
Inline variable preview (same breakage as above)
With 78: Now also mapping in Logpoints (making logging work for original variables)
Problem
The checkbox is so subtle that it's easy to ignore, so users lose out on a better debugging experience.
Solution
Lightweight onboarding to opt users into enabling Map scopes when it's available for a file.
This could be a subtle bar in the Scopes pane on pausing or on top of the file as a lot of variable inspection happens in context of the code.
The text was updated successfully, but these errors were encountered:
If I understand correctly, we'd display similar notification message explaining what "Map Scopes" does and perhaps link to MDN - directly within the "Scopes" panel at the top?
I am also attaching a screenshot of what we do for the multi-line Console editor
Background
Map scopes transforms build/compressed into how the original source behaves. It's magical when enabled buy we can't enable it by default as it has performance overhead (especially on the first pause).
It makes several variable-related features more reliable:
Problem
The checkbox is so subtle that it's easy to ignore, so users lose out on a better debugging experience.
Solution
Lightweight onboarding to opt users into enabling Map scopes when it's available for a file.
This could be a subtle bar in the
Scopes
pane on pausing or on top of the file as a lot of variable inspection happens in context of the code.The text was updated successfully, but these errors were encountered: