Add quick fix for sealed class within empty switch expression. #3345
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.
@jjohnstn I noticed you did a loooot of good refactoring in the local corrections subprocessor. However I want to properly implement that later, because it's a bit of a manual process. I basically need to go to every copied implementation in the JDT-LS local subprocessor, confirm the base processor in jdt.core.manipulation does things identically (ie. JDT-LS hasn't added any hacks for odd reasons), and if so, delegate to it and reduce duplication. Is it ok if I leave some of those abstract methods unimplemented for now ? We don't currently call them in JDT-LS and it appears they're only called from JDT UI's LocalCorrectionsSubProcessor (which we don't use).
Screencast.from.2024-12-17.17-12-46.mp4