microsoft / microsoft/copilot-for-eclipse
[Bug] There a a lot of didChange notification with empty payload
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Some of them even come before initialize
{"jsonrpc":"2.0","method":"copilot/hook/didChange","params":{}}
{"jsonrpc":"2.0","method":"copilot/customAgent/didChange","params":{}}
{"jsonrpc":"2.0","method":"copilot/customPrompt/didChange","params":{}}
{"jsonrpc":"2.0","method":"copilot/customInstruction/didChange","params":{}}
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 tracing the Java handling of the copilot/hook/didChange, copilot/customAgent/didChange, copilot/customPrompt/didChange, and copilot/customInstruction/didChange notifications. Reproduce initialization and verify that these notifications are not emitted with empty params or before initialize.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100