Ruby LSP adoption
Open
@vinistock is already working on this.
Since Apr 20, 2026.
- Dominant language
- Rust
- Stars
- 355
- Forks
- 24
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 17
Description
One of the main goals of Rubydex is to have it be the code intelligence engine for the Ruby LSP. To make adoption gradual and allow us to find bugs, we're going to cut beta releases of the LSP as we adopt Rubydex.
The steps to fully adopt Rubydex are:
Foundation
- Add Rubydex as a dependency https://github.com/Shopify/ruby-lsp/pull/3991
- Start performing initial indexing and resolution on boot https://github.com/Shopify/ruby-lsp/pull/3992
- Update the Ruby LSP's singleton class name representation to match Rubydex's https://github.com/Shopify/ruby-lsp/pull/3993
- Migrate Ruby LSP's type inferrer to use Rubydex graph https://github.com/Shopify/ruby-lsp/pull/4014
- Start consuming incremental changes upon edit and on file watched notifications https://github.com/Shopify/ruby-lsp/pull/4032
Features
- Go to definition https://github.com/Shopify/ruby-lsp/pull/4015 https://github.com/Shopify/ruby-lsp/pull/4095
- Hover https://github.com/Shopify/ruby-lsp/pull/4029 https://github.com/Shopify/ruby-lsp/pull/4097
- Signature help https://github.com/Shopify/ruby-lsp/pull/4098
- Completion https://github.com/Shopify/ruby-lsp/pull/4096
- Workspace symbol https://github.com/Shopify/ruby-lsp/pull/4019
- Rename https://github.com/Shopify/ruby-lsp/pull/4033
- Find references https://github.com/Shopify/ruby-lsp/pull/4066
- Type hierarchy https://github.com/Shopify/ruby-lsp/pull/4072
- Test discovery (we use ancestors to detect test framework) https://github.com/Shopify/ruby-lsp/pull/4064
Add-ons
- Migrate Rails add-on to Rubydex
- Migrate Tapioca add-on to Rubydex https://github.com/Shopify/tapioca/pull/2620
Documentation
- Remove type hierarchy from experimental (it should be a stable feature now)
- Review if any add-on related APIs need to be documented again
Clean up
- Remove all code related to the old indexer https://github.com/Shopify/ruby-lsp/pull/4101
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.
Assessment
This issue has not been assessed yet.