Add reason field to Breakpoint
#825
Closed
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
According to the specification, the Breakpoint type must have `reason` optional field. This field was introduced in microsoft/debug-adapter-protocol#437.
|
Thanks for the submission. I'm therefore not sure what to do with this pull request. Hopefully someone can implement 1.61-1.64 (or 65) so I don't need to decide how to handle this special case. Would you like to submit a PR to upgrade to 1.64 or 1.65? |
|
Yes, I would like to prepare PR with an upgrade to the latest version. Then this one should be included in it. Thank you! |
|
That is great @Soarex16 - I look forward to reviewing it when you are ready. |
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.
According to the specification, the Breakpoint type must have
reasonoptional field. This field was introduced in microsoft/debug-adapter-protocol#437.