Output index in lsif format
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2k
- Forks
- 281
- Avg merge
- 2h 14m
- Merged PRs (30d)
- 6
Description
I have checked that this feature is not already implemented
- This feature does not exist
Use case
Lots of tools online use the lsif file format to provide "smart" features related to a codebase. One of them is navigating around the codebase by clicking on class names in SCM tools (like GitLab). This project generates an index internally, used for navigating though the codebase, but it's not dumped to a file, and it doesn't use the lsif format.
Description
The index that ruby-lsp generates is dumped into a lsif file that I can use with other tools.
Implementation
No response
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
The issue names no files, tests, or entry points. Start by locating how ruby-lsp builds its internal index and by reviewing the LSIF format requirements. Done means the generated index can be dumped to an LSIF file for use by external code-navigation tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100