redhat-developer / redhat-developer/lsp4ij
Is there any mechanism for tracking timing of analysis features end-to-end?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
Since we are migrating analysis features from our own client-side implementation to using lsp4ij and a different set of language server endpoints, we're interested in tracking how long it's taking for features to work end-to-end. Are there any mechanisms in place in lsp4ij to allow for this?
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 searching the lsp4ij repository for existing timing, tracing, metrics, or request instrumentation around language-server endpoints. Compare any available measurements with the end-to-end analysis features described here and document whether they cover the migration. Done means a concrete answer about existing support or a scoped proposal for adding it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100