redhat-developer / redhat-developer/vscode-yaml
modifySchemaContent does not update the linter
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 830
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
When using the modifySchemaContent it update the schema but does not validate the file with the new values added to the schema.
Expected Behavior
When calling the modifySchemaContent the linter squiggles should update validating the new values.
Current Behavior
The linter continues with the squiggles even though the values are valid.
Steps to Reproduce
- YAML file using an enum value that is not valid
- call modifySchemaContent and add the value
- Check that the value is still not valid
Environment
- Windows
- Mac
- Linux
- other (please specify)
ALL
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
Search for the modifySchemaContent entry point and trace how schema changes reach linter diagnostics. Reproduce the enum-value case from the issue, then verify that adding the value removes the existing squiggle and add or update coverage if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100