resolveDebugConfiguration returns null to tell vscode to continue generating launch.json #430
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
…erating launch.json Signed-off-by: Jinbo Wang <jinbwan@microsoft.com>
Eskibear
approved these changes
Sep 18, 2018
andxu
approved these changes
Sep 18, 2018
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.
Signed-off-by: Jinbo Wang jinbwan@microsoft.com
Follow the issue microsoft/vscode#54213 (comment), in order to generate launch.json, the resolveDebugConfiguration api must return null explicitly.
This PR doesn't affect current vscode behavior, but prevent the future break change from the vscode insider. So i prefer to change vscode java debug source code in advance.