Fix: Open .java file instead of .class during debugging when source is available#4375
Open
amritamishra01 wants to merge 1 commit intoredhat-developer:mainfrom
Open
Conversation
Collaborator
|
I believe the proper fix should happen in microsoft/java-debug#623 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
Currently, when debugging Java classes, the extension attempts to open the
.classfile instead of the corresponding.javasource file, even when the source is available.Fix
.javafile exists for the given URI..javafile instead of the.classfile..classfile if source is not available.🔧 Changes
javaClassEditor.tsto resolve correct file URI dynamically.Result
Improves debugging experience by showing readable source code instead of compiled
.classoutput.fixes #4356