redhat-developer / redhat-developer/vscode-yaml
Erroneous schema detection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
I have file .github/workflows/build.yaml , which is highlighted red with this error:
Property name is not allowed. yaml-schema: gRPC API Gateway & OpenAPI Config
The file has nothing to do with gRPC or OpenAPI and should not be checked as such.
Expected Behavior
Do not use schema for gRPC & OpenAPI with github woskflows file.
Current Behavior
File is checked against wrong schema.
Steps to Reproduce
- Install YAML extension
- Create file .github/workflows/build.yaml with some standard Github Workflow
- See that errors would appear from wrong schema
Environment
- Ubuntu 24.04
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 issue by installing the YAML extension and opening a standard .github/workflows/build.yaml file in VS Code. Trace how the file is assigned the gRPC API Gateway & OpenAPI schema, then verify that GitHub workflow files are checked with the appropriate schema and no unrelated errors appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode, yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100