redhat-developer / redhat-developer/yaml-language-server
Allow CustomSchemaProvider to provide schema content instead of uri
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 352
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 11
Description
Is your enhancement related to a problem? Please describe.
A Lsp Client can implement custom schema selection by using the CustomSchemaProvider.
This only allows the client to return a uri to the schema to be used.
For my usecase the client is generating the schema on the fly.
Only being able to return a uri adds an additional roundtrip that could be avoided.
Describe the solution you would like
Allow the CustomSchemaProvider to directly return the schema as json.
Describe alternatives you have considered
Additional context
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 CustomSchemaProvider and the code that consumes its returned schema URI. Trace how a client-provided schema is selected and fetched, then define the response path for directly supplied JSON content while preserving URI-based behavior. Done means generated schema content can be returned without the extra roundtrip.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100