docs: add guide for using custom model names with acts_as helpers #171
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Extend the Rails guide to explain how to customize model names when using the acts_as_chat, acts_as_message, and acts_as_tool_call helpers.
|
closes #183 |
crmne
requested changes
Jun 11, 2025
There was a problem hiding this comment.
Thanks @matheuscumpian. Only a couple changes needed before merging.
|
@matheuscumpian want to resolve the requested changes? |
|
@crmne thanks for the review and sorry for the lateness, I've just addressed the comments on a new commit |
crmne
approved these changes
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While integrating RubyLLM with an existing Rails application that already had a
Chatmodel, I discovered that the framework supports using custom model names with theacts_ashelpers. This isn't explicitly documented, but is a valuable feature for real-world Rails applications where naming conflicts or existing conventions might exist.Let me know if I'm missing something on this behaviour