-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Vscode : Case sensitive issue is back #1341
Comments
What does this mean? To help us debug this issue can you explain:
|
(and others that have both upper and lower case characters in the extension id |
This was originally opened as #1302 |
I cannot reproduce on multiple levels:
As a result, it seems likely that you are on an old version of homebrew-bundle, can you check please? If you are not:
Please provide minimal input data here.
And provide minimal commands. These should not all be necessary to reproduce. Ideally: try to open a PR. Thanks! |
thanks @MikeMcQuaid .
Here's my investigation: When I go into VSCode, go to the Extensions view, click on 1 of the extensions, (for eg editorconfig), click on the gear icon, and select the "Copy Extension ID", the text that's copied is NOT all lowercase. I would assume that any other user is also following similar steps when adding a new extension, they follow the same steps. For the editorconfig extension, the text that's copied is If I run |
@vraravam I know the text is not always lowercase. My point is: even if it is lowercase we only compare lowercase names to lowercase names. Even when I edit my |
this was fixed in an earlier PR that I had raised a couple of months ago, and it had been fixed at that time. But, when I rerun the same commands now, the vscode extensions that have upper and lower case characters in the extension id are now being cleaned up forcibly.
My Brewfile is here: https://gist.github.com/vraravam/8c9eae91a3750bed86b81e3a4711f842
I can confirm that only those extensions that have both upper and lower case characters are affected.
The text was updated successfully, but these errors were encountered: