redhat-developer / redhat-developer/vscode-yaml
Extension config inside devcontainer.json is ignored
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
I have this in my .devcontainer/devcontainer.json:
{
"name": "test",
"build": {
"dockerfile": "Dockerfile",
"context": ".."
},
"customizations": {
"vscode": {
"settings": {
"yaml.format.enable": true,
"yaml.schemas": {
"./my_schema.json": "*.yaml",
},
"yaml.maxItemsComputed": 80001
},
"extensions": [
"redhat.vscode-yaml"
]
}
}
}
This does not work. When the dev container launches non of those settings are applied. I have to put those settings in a .vscode/settings.json file for the extension to use them.
I have not seen this with other extensions before, they all seem to pick up settings defined in devcontainer.json without issues.
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.
Research direction
Reproduce the report using the shown .devcontainer/devcontainer.json and compare the extension behavior with settings in .vscode/settings.json. Trace how the YAML extension receives settings when launched in a dev container; done means the listed YAML settings are applied from devcontainer.json, including the schema, formatting, and item limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100