redhat-developer / redhat-developer/vscode-yaml
docker-compose.test.yaml file is using prometheus.rules.test.json first
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Is your enhancement related to a problem? Please describe.
I have three compose files:
docker-compose.development.yamldocker-compose.production.yamldocker-compose.test.yaml
For docker-compose.test.yaml extension suggests prometheus.rules.test.json first and validates with that. Which is incorrect because my file is a compose file it starts with docker-compose.
Describe the solution you would like
Files start with docker-compose should be detected as a compose file first.
Describe alternatives you have considered
I can change with settings.json locally however this seems to a valid issue to me.
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 association choice with docker-compose.test.yaml and compare it with prometheus.rules.test.json. Start by tracing the extension's file-detection ordering, using settings.json only as a reference for the current workaround; done means files beginning with docker-compose are detected as compose files first without breaking the other named compose files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100