Skip to content

Ruby LSP adoption #669

@vinistock

Description

@vinistock

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

Features

Add-ons

  • Migrate Rails add-on to Rubydex
  • Migrate Tapioca add-on to Rubydex (no-op, I think)

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No fields configured for Epic.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions