Closed UnnamedXAer closed 3 months ago
Looks similar to https://github.com/eclipse-jdt/eclipse.jdt.core/issues/1641. Maybe this is another way of triggering the problem that hadn't been predicted upstream.
Was able to easily reproduce by calling code completion in a source file that extends a sealed class.
Update: This is reproducible in upstream Eclipse as well.
This has just been fixed upstream. As soon as a build is available of JDT (from today), I can update this in the language server and have this in our pre-releases (towards 1.32.0 for end of month).
I'm not able to use rename, quick fix, go to definition when editing class that extends sealed class.
Environment
Steps To Reproduce
[Please attach a sample project reproducing the error] https://github.com/UnnamedXAer/java_language_server_issue_sealed
logs
https://github.com/UnnamedXAer/java_language_server_issue_sealed/blob/master/README.md#full-log
Current Result
Popup saying 'Internal error';
Expected Result
Rename box;
Additional Informations
In more advanced scenarios (classes) most of the LSP related features do not work.