-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organize Imports sometimes doesn't work #50
Comments
In:
Which would seem to explain the non-working organize imports (although it might also affect the quick fixes). It is unfortunately quite difficult to know what's wrong from the stack trace - a reproducible testcase would be awesome. |
If I run into this again, I'll make sure to provide a reproducer. It would be good if - whenever an exception occurs - the content of the file that caused the issue would be dumped to the log as well. So if I don't report the issue immediately, I can still provide the code that caused the exception. |
Organize Imports doesn't work with the file below. package be.anthonyv.ab.cdefgh.xyz.abcdefoobar;
import java.nio.file.Files;
class GenerateIndex {
private static final Path FOO = Path.of("");
public static void main(String... args) {
var contents = Files.readString(FOO);
}
}
|
At the start, I had no imports.
The logs only say:
I ended up importing everything via the quick fixes one by one. The required imports were:
Extension version 1.0.0 with VS Code
Version: 1.83.1 (user setup)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:48:05.904Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621
The text was updated successfully, but these errors were encountered: