Open sean-mcmanus opened 4 years ago
Found a repro: use code <path to workspace with the wrong casing>
(there could be other ways to repro this too).
The code tries to use the "correct" casing instead of the "wrong" case that VS Code is using, so it is skipping the IntelliSense errors when it finds the cases don't match. Not sure if this is related to the recent VS Code changes related to casing, but from our side the issue has existed for a long time.
We think this might be a VS Code issue. They were supposed to have addressed casing issues with URI's.
@bobbrow Should I file a VS Code bug?
Yes, please.
I don't think it's a VS Code bug. The VS Code issue was https://github.com/microsoft/vscode/issues/12448 . They fixed it, but the problem is that VS Code itself using only 1 URI casing, but the problem is that we're internally changing that casing. I think we'd need to change our code to respect that casing that VS Code uses.
Something can cause VS Code to open a folder with the wrong casing, causing IntelliSense errors to not appear. I don't know how to get VS Code to behave that way though. The workaround is to open the folder with the correct casing. Let me know if anyone knows how to cause the wrongly cased folder to be opened with VS Code. I'm not sure if there's a way we can fix this or we should file a VS Code bug.