Case-sensitivity when opting out of VSCode extensions
@chrmarti is already working on this.
Since Oct 11, 2024.
Assessment
This issue has not been assessed yet.
Description
- VSCode Version: 1.94.1
- Local OS Version: macOS 14.2
- Remote OS Version: Debian GNU/Linux 11 (bullseye)
- Remote Extension/Connection Type: Containers
Steps to Reproduce:
- Add a feature that installs an extension in the
devcontainer.jsonfile, for example, the aws-cli feature:
"features": {
"ghcr.io/devcontainers/features/aws-cli:1": {}
}
- Opt out of the extension using the following configuration:
"customizations": {
"vscode": {
"extensions": [
"-amazonwebservices.aws-toolkit-vscode"
]
}
}
Issue:
After launching the container, the extension is still present. In the feature, the extension's ID is written with uppercase letters: "AmazonWebServices.aws-toolkit-vscode". To make it work, you need to write it with the same casing:
"customizations": {
"vscode": {
"extensions": [
"-AmazonWebServices.aws-toolkit-vscode"
]
}
}
This should not be necessary. The check should not be case-sensitive.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-remote-release
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-remote-release#11650 ·
-
ssh
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/vscode-remote-release#11583 ·
-
ssh
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/vscode-remote-release#11861 ·
-
microsoft/vscode-remote-release#11860 · 1 comment · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/vscode-remote-release#11859 ·