redhat-developer / redhat-developer/vscode-yaml
Migrate "retry after delay" from yaml-language-server to vscode-yaml
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
This doesn't work in vscode-yaml, since we use the custom endpoint to request the schema and don't go through this code path. We'll need to provide a similar functionality there in a separate PR. The VS Code endpoint seems to have some sort of rerequesting logic already, so we'll need to work around that.
Originally posted by @datho7561 in https://github.com/redhat-developer/yaml-language-server/pull/1342#pullrequestreview-5251900325
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
Trace how the custom endpoint requests schemas in vscode-yaml and compare it with the existing retry-after-delay behavior in yaml-language-server. Read the VS Code endpoint's rerequesting logic and determine how equivalent retry behavior can work around it. Done means the custom endpoint supports retry-after-delay without conflicting with VS Code rerequests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, yaml
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100