Extending Ruby LSP with Prism
The article discusses the extension of Ruby LSP using Prism to enhance the coding experience in Ruby projects. It highlights the implementation of a 'go to definition' feature for render calls in view templates, which was previously available in rails.vim. The author provides insights into the mechanics of language servers and the process of creating custom add-ons for Ruby LSP.
- ▪Ruby LSP is built on top of Prism, Rubydex, and RBS, offering various features for Ruby code editing.
- ▪The author transitioned from Vim to Zed and found Ruby LSP to provide modern editor functionalities.
- ▪The article details how to implement a 'go to definition' feature for render calls in Ruby LSP.
2 outlets in our directory ran this story, first to last over 7 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Extending Ruby LSP with Prism — r/ruby
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Janko Marohnić |
| Canonical URL | https://janko.io/extending-ruby-lsp-with-prism/ |
| Publication time | Wed, 27 May 2026 04:13:56 +0000 |
| Retrieval time | 2026-05-27T04:37:56.807Z |
| Last seen | 2026-05-27T04:37:56.807Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 6cclcd285rEo · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
May 26, 2026 Extending Ruby LSP with Prism Ruby LSP is a wonderful language server built on top of Prism, Rubydex and RBS. It implements a variety of features that enrich the code editing experience in Ruby projects. Its add-on architecture allows extending it with Rails features, Rubocop support and custom functionality. Coming from Vim, I was really used to rails.vim. When I switched to Zed, I started using Ruby LSP. In some ways I felt like I’ve gained superpowers, as now I had all these modern editor features that are possible because my Ruby code is actually being parsed. On the other hand, I found there were some features I was missing. One such feature was following render calls in view templates.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Janko Marohnić.
Discussion
0 commentsMore from Janko Marohnić
