A Rails server in your editor: Using Ruby LSP to extract runtime information
summary
Shows that the Ruby LSP actually hooks into a running Rails process to read live state rather than guessing from source, surfacing database schema, migrations and pending migrations, and the app’s routes and controller actions inside the editor. Demonstrates Ruby LSP Rails as an extendable bridge that queries the runtime, reduces wrong completions from metaprogramming, and reliably updates editor features as migrations or routes change during development.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:27Ruby LSP overview
- 10:28Editor integration demo
- 20:03Runtime data extraction
- 27:58Conclusion and Q&A
