Update DWDS to handle JS variables that are unavailable in the current scope
Open
P3
package:dwds
triaged
waiting-for-customer-response
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Description
Changes to Chrome DevTools could change the properties visible in a scope or change their value to signal that they are not available. DWDS should be made resilient to these changes as they could come from future V8 optimizations.
Contributor guide
Research direction
Start by tracing DWDS handling of JavaScript variables in the current scope, focusing on how scope properties are represented when Chrome DevTools changes their visibility or value. Identify the affected behavior and add coverage for unavailable variables, with the implementation remaining resilient to future V8 optimizations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100