redhat-developer / redhat-developer/yaml-language-server
Operations don't work without textDocument/didOpen
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 352
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 11
Description
According to https://github.com/Microsoft/language-server-protocol/issues/177 operations should work even if textDocument/didOpen was not called for a language server. Opening a document or closing it only shifts where the content is managed (in memory or on disk) but shouldn't prevent an operation.
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
No file or test is identified. Start by tracing how language-server operations handle requests when textDocument/didOpen has not been called, using the linked LSP issue 177 for context. Done means opening or closing a document no longer prevents operations when content is managed on disk or in memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100