Skip to content

refactor: create three distinct Rails classes, InputRails, OutputRails, and DialogRails #1151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
5 tasks
Pouyanpi opened this issue Apr 28, 2025 · 0 comments
Open
5 tasks

refactor: create three distinct Rails classes, InputRails, OutputRails, and DialogRails #1151

Pouyanpi opened this issue Apr 28, 2025 · 0 comments
Labels
enhancement New feature or request refactoring

Comments

@Pouyanpi
Copy link
Collaborator

Pouyanpi commented Apr 28, 2025 •
edited
Loading

based on config, LLMRails (composer) picks or assembles the right pieces. Users can still explicitly pick one mode, or get “everything” under one roof.

we need an abstract base, concrete single purpose implementations, and a small factory/composite to glue them under LLMRails umberella for example.

  • introducing BaseRails
  • extracting three single responsibility implementations
    • InputRails
    • OutputRails
    • DialogRails
@Pouyanpi Pouyanpi added enhancement New feature or request refactoring labels Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Pouyanpi