Repository navigation
Add Hybrid LSP support for Ruby #1701
Description
What problem does this solve?
Most of our applications are ruby apps - providing Hybrid LSP support for ruby applications makes this tool more valuable to us.
Proposed solution
Provide Hybrid LSP support for the Ruby language.
Alternatives considered
No response
Confirmations
- I searched existing issues and this is not a duplicate.
Activity
DeusData commentedon Aug 18, 2026
Thank you for opening the language request first. The linked implementation in #1706 is now the review route for this work. Ruby Hybrid LSP support is broader than an extension mapping, so the review will check deterministic import, call, usage, inheritance, and fallback behavior before any merge decision. The contribution queue is full, but this is now labeled and tracked rather than waiting without a route.
fix(extraction): keep Ruby superclass names bare
fix(extraction): keep Ruby superclass names bare
DeusData commentedon Oct 25, 2026
Thank you for the Ruby request. #1706 remains the review route identified earlier; I have no new review outcome to report. Sorry for the delay; this is waiting on maintainer follow-up, and I’ll follow up soon.
fix(extraction): reduce A::B.new callee to the constant
feat(lsp): add the Ruby per-file resolver