-
Notifications
You must be signed in to change notification settings - Fork 37.6k
workspace folders map should ignore path casing unless linux #110224
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
Conversation
sandy081
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Note: Did not verify the fix.
|
While this improves the situation with the |
|
Ok, an issue remains, and that is that the Code pointer where I use it To repro on Win
|
|
Ok here it is
Checking if changing it there also helps... |
|
Yeah, that would also have to be changed. I have verified with that change that the issue is fixed. |
|
This code is actually literally copied from how @jrieken had it before I rewrote file service. I think it should use the file system provider's capability for the ternary tree there as well. |
|
@bpasero yeah I just pushed that. Please review and let me know what you think. |
bpasero
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment. Created #110241 for the actual solution.
| // lazy trie to check for recursive resolving | ||
| if (!trie) { | ||
| trie = TernarySearchTree.forUris<true>(); | ||
| trie = TernarySearchTree.forUris<true>(!this.hasCapability(resource, FileSystemProviderCapabilities.PathCaseSensitive)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use isPathCaseSensitive in that file
|
Hm... Should we simply bring back the old behaviour instead of picking on a few places? |
|
@jrieken yeah that might be best. |
|
closing and creating another PR which basically undoes my initial refactoring |
This PR fixes #110188