-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Imports are incorrectly sorted and/or formatted. #20029
Comments
You can ignore that if you have not edited the file. But the check comes from |
@luabud @cwebster-99 I think we need a setting to turn of import checking. What do you think? |
This StackOverlow says it's throwing this warning when there is only one import. (Hence properly sorted.) Also that QuickFix solves the issue temporarily, and without changing the file. Warning reappears on close/open. I'm seeing it flag a comment on either the first line of the file or the first import, regardless what import I put first. It offers no QuickFix. |
@ctwardy the warning is shown based on what is seen when you run |
@ctwardy you should be able to see the output from |
OK, thanks, I'll take a look. |
@karthiknadig Can you exactly show the steps to solove the problem! I can not understand,Thanks |
In |
Type: Bug
Type:bug
Imports are incorrectly sorted and/or formatted.
I haven't touch any code.
Extension version: 2022.17.12911022
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:15:18.074Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No
Connection to 'ssh-remote+3070' could not be established
Remote OS version: Linux x64 5.4.0-124-generic
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Connection to 'ssh-remote+3070' could not be established
A/B Experiments
The text was updated successfully, but these errors were encountered: