You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add provider specifying example to rails guide (#233)
## What this does
Provide similar example that answered #226
## Type of change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [X] Documentation
- [ ] Performance improvement
## Scope check
- [X] I read the [Contributing
Guide](https://github.com/crmne/ruby_llm/blob/main/CONTRIBUTING.md)
- [X] This aligns with RubyLLM's focus on **LLM communication**
- [X] This isn't application-specific logic that belongs in user code
- [X] This benefits most users, not just my specific use case
## Quality check
- [X] I ran `overcommit --install` and all hooks pass
- [X] I tested my changes thoroughly
- [X] I updated documentation if needed
- [X] I didn't modify auto-generated files manually (`models.json`,
`aliases.json`)
## API changes
- [ ] Breaking change
- [ ] New public methods/classes
- [ ] Changed method signatures
- [X] No API changes
## Related issues
<!-- Link issues: "Fixes#123" or "Related to #123" -->
Related to #226
---------
Co-authored-by: Carmine Paolino <[email protected]>
Copy file name to clipboardExpand all lines: docs/guides/rails.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,6 +193,29 @@ class ToolCall < ApplicationRecord
193
193
end
194
194
```
195
195
196
+
### Setup RubyLLM.chat yourself
197
+
198
+
In some scenarios, you need to tap into the power and arguments of `RubyLLM.chat`. For example, if want to use model aliases with alternate providers. Here is a working example:
0 commit comments