Repository navigation
Can't get rid of 'Name source files using lowercase_with_underscores.dart(file_names)' #3236
Description
Hi all, love what you doing.
Yesterday renamed one of my widgets from tracking_sheet.dart to Measure_sheet.dart. Of course got warning, immediately renamed it to measure_sheet.dart, but warning didn't go away.
Renamed it to Kmeasure_sheet.dart, then back to measure_sheet.dart, the warning appeared again:
I tried also removing file from the project and re-adding - no luck.
Please help how can I kill the warning.
Best regards,
Dmitry
Activity
DanTup commentedon Mar 29, 2021
I'm not able to reproduce this, the error disappears once I rename the file back. In the logs I can see the server sending an update to clear them.
Could you try capturing a log?
Note: The log file may include parts of your source code so it would be better to reproduce on a small sample project, but otherwise be sure to check the log for anything sensitive before sharing.
Thanks!
Asperson commentedon Mar 29, 2021
I was able to reproduce it on a small project, copying and reducing existing measure_sheet.dart.
One note - I renamed file in the vscode using F2 in the project tree, not externally.
After vscode loaded the file looked correctly but then if I click another file and return back to this one it become reported having incorrect cases in its name.
Dart-Code-Log-2021-02-01 11-38-48.txt
vscode v1.54.3 (user setup)
dart-code v3.20.1
DanTup commentedon Mar 29, 2021
Strange - I renamed the same way, though no luck. I tried on Windows too but it seemed fine (I tried both changing only the casing, and also changing the casing and adding more letters at the same time).
Can you confirm exactly what sort of rename you're making? If I can't repro, I'll see if I can trace through the server how this is normally handled to see if I can come up with any theories for why it wouldn't be happening for you.
Thanks!
Asperson commentedon Mar 30, 2021
I think I found the way to reproduce bug:
After these steps on my machine (windows 10) all content in bb_aa.dart undercrossed with blue line and Problem window shows a case problem for Bb_aa.dart file
add2project.zip
cto-leaps commentedon Apr 11, 2021
I have the same issue on Mac OS, but the error is only shown whenever I make any change to the file and remains until I save the file again. Then it disappears. Makes it hard to edit a file...
DanTup commentedon Apr 12, 2021
Aha! I couldn't repro with the instructions above, but when I modified the file the error appeared again. I'll do some digging. Thanks!
DanTup commentedon Apr 12, 2021
Also - after restarting VS Code I could repro it the original way - just renaming the file to Bb and then back to bb - the error remained.
DanTup commentedon Apr 12, 2021
This feels like a VS Code bug. When I change the casing of a file, then reload VS Code, then close and re-open the file, VS Code still keeps giving me the old case - even though it shows the new casing in its UI.
I've opened microsoft/vscode#121106 to get some clarification (but it's not clear based on microsoft/vscode#102627 whether this is intended or not).
48 remaining items
Omi231 commentedon Aug 12, 2022
deleting
User/workspaceStorageinside(C:\Users*USERNAME*\AppData\Roaming\Code)worked for me.jaidex commentedon Aug 16, 2022
I've found evidence that this may be related to an unchanged reference to the old file name in another file (in and import).
Note: to do this, I DID first follow the standard clean-up steps as stated above, however, the fact that it exposed the usage of the original, caps-included name which had been renamed a LONG time previously, makes me think there's a related issue there.
As long as the original file had not been physically removed from the project and replaced with an old one, the import with the pre-changed name was still working, though the name was NOT the same.
DanTup commentedon Aug 22, 2022
@jaidex are you able to reproduce that issue? I can't think of a reason why a mismatched import would trigger this issue (although I can imagine it could cause some other issues while running/debugging). If you can reproduce it, or if the
dart.normalizeFileCasingsetting doesn't prevent it, I'd definitely like to understand why it's failing.Thanks!
Lorenzohidalgo commentedon Oct 7, 2022
@DanTup it looks like this issue has "re-surfaced" at least in our case.
Here are the versions we are working with that show the incorrect warning:
Flutter: v3.3.3
Dart: v2.18.2
VSCode: v1.72.0
Dart Code Extension: v3.50.0
DanTup commentedon Oct 7, 2022
@Lorenzohidalgo do you have the
dart.normalizeFileCasingsetting enabled? If so, can you capture a log as described in this comment above? Thanks!Lorenzohidalgo commentedon Oct 7, 2022
@DanTup sorry, I didn't have that config initially enabled.
I've reproduced the steps mentioned in the linked comment but could not reproduce our error with either
dart.normalizeFileCasingset toselectedorunselected.In our case, this issue happened initially on my colleague's system and "passed" on to me when I pulled the changes. There was no "file name change" happening on my computer and I can only dismiss the warning by adding
// ignore_for_file: file_namesto the files.I'll try to reproduce all steps again while capturing the logs. Since the "use case"/issue is not precisely the same, should I share them on this issue or create a new one?
DanTup commentedon Oct 7, 2022
@Lorenzohidalgo do you mean the issue has gone away now and you can no longer reproduce?
If you can reproduce an issue with
normalizeFileCasingenabled, please do file a new issue.normalizeFileCasingis a bit of a hack and not the real solution, but it's all we have right now. Unfortunately the real fix is rather complicated because it requires VS Code, LSP and the Dart server to all agree on how case sensitivity should work, but right now VS Code is basing its case sensitivity purely on platform (which is not always correct, and makes it perhaps not a great model for LSP/language servers to follow).PeterHenter commentedon Jan 29, 2023
I had the same issue.
My versions are as follows:
Flutter 3.7.0,
Dart is 2.19.0
Visual Studio Code 1.74.3
VSC Flutter extension v3.58.0
VSC Dart extension v3.58.0
What I noticed is, that only 1 file was affected in the entire project. The file was originally called
Buttons.dart. After renaming the file in the VSC Explorer pane tobuttons.dartthe file name changed in the Explorer pane but remained the same on tab in the Editor, and the linter kept complaining.I managed to fix the issue by inserting an underscore at a random location in the file name, like
button_s.dart. After this the warning disappeared. I then closed VSC, then reopened it, and renamed the file again back tobuttons.dart. And the warning did not come back.DanTup commentedon Jan 30, 2023
Ah, that's good to know. My guess is when you make a change to the filename that is more than just casing, then VS Code does change the internal model, which removes the old casing. Renaming only by the case likely does not. If it works reliably, this might be a better workaround than using
normalizeFileCasingsince that introduces a small performance penalty.sanba-anass commentedon Sep 30, 2024
issue presist it's annoying since i'm using code gen with mobx and i'm getting an error saying unmatching file of 'part' and 'part of ' even i f i rename it to the correct file naming convention so odd
BlarCkat commentedon Oct 1, 2024
@sanba-anass can you take a screenshot of the problem?
DanTup commentedon Oct 1, 2024
@sanba-anass that sounds like a different issue, but it's hard to diagnose without seeing the code. Feel free to open a new issue including a sample project or screenshots that show both of the files in question and the error you're seeing and I'll try to help. Thanks!
larssn commentedon Mar 30, 2025
FYI this issue still exists, but managed to fix it with the above workaround.
hosmoon commentedon Apr 30, 2025
I love you.
I solve that problem as add _ method.
Thanks!