redhat-developer / redhat-developer/vscode-yaml
Allow `yamlValidation` to be defined programmatically
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.
Nope.
Describe the solution you would like
The contributes.yamlValidation functionality works great, but we want to use versioned schemas without having to continuously update the extension.
Since package.json is static, these schema URLs are also static.
It would be nice, if possible, to set yamlValidation programmatically through the JS extension.
Describe alternatives you have considered
N/A
Additional context
N/A
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
Start by locating the implementation of contributes.yamlValidation and the JavaScript extension integration. Trace how static schema URLs from package.json are registered, then determine the extension-facing entry point for defining them programmatically. Done means versioned schema URLs can be supplied by an extension without continuously updating its manifest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100