DAP: add expensive field to scopes type.
#1347
Merged
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
There's a required `expensive` field on the Scope Type used to hint to the client whether the variables in the given scope are expensive to retrieve. https://microsoft.github.io/debug-adapter-protocol/specification#Types_Scope
|
For a quick fix for clients that need this field we can just hard-code to |
|
Nice catch. @TheGeorge do you have any opinions on this? |
robertoaloi
approved these changes
Jul 4, 2022
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.
Description
There's a required
expensivefield on the Scope Type usedto hint to the client whether the variables in the given scope are
expensive to retrieve.
https://microsoft.github.io/debug-adapter-protocol/specification#Types_Scope