spring-projects / spring-projects/spring-tools
[spring index] avoid sending super type information over the LSP wire
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
The internal structure of the beans in the new spring index contains information about super types, but this information should be internal only to the spring index and should not be transferred over the wire when clients ask for the beans of the spring index via the LSP communication.
That way, we can optimize the internal structure (e.g. #1045) without worrying about breaking clients who use this internal information.
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 the Spring index bean representation from its internal structure to the LSP communication boundary. Confirm that super type information remains available internally but is omitted from bean data sent to clients, then verify the client-facing response shape and relevant index behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100