Replies: 1 comment 1 reply
-
|
No. The rails integration is 532 lines of code, not loaded unless you're running RubyLLM inside Rails, and it adds no dependencies to the library. Splitting it out would mean releasing, maintaining, and synchronizing two gems for no practical benefit.
As your colleague’s 7.6k+ line POC shows, it doesn’t. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What do you think about extracting the rails integration into a separate gem, much like how the MCP stuff lives in a separate gem?
I have a colleague who built a large POC (+7.6k lines) using this gem but not using the rails integration bits at all. I know there are pros and cons of rolling your own vs using a larger, community-supported project, but I'd feel a lot better about rolling our own if the large, community-supported project wasn't also pulled in as a result of
require "ruby_llm".It would also be nice to ensure that dependency on the rails integration doesn't sneak into the non-rails portions of RubyLLM gem
Beta Was this translation helpful? Give feedback.
All reactions