Fix Local Variable Display in Debugger for React Native Windows #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![cosineai[bot]](https://avatars.githubusercontent.com/in/705948?s=60&v=4){kind=small}
Co-authored-by: Genie <genie@cosine.sh>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses the issue where local variables were not being displayed in the Variables section when debugging a React Native Windows application in VS Code. The problem was due to missing implementations for handling scope and variable requests in the DirectDebugSession class.
Changes Made:
scopesRequestmethod to define the local scope for the current frame.variablesRequestmethod to fetch and display variables for the defined scope.These changes ensure that when a breakpoint is hit, the local variables are correctly displayed in the debugger, and variables added to 'Watch' are evaluated properly.
This fix resolves the error message 'Uncaught Error: Can't evalInFrame: Environment not found' and improves the debugging experience by allowing developers to inspect local variables as expected.