Splitting model in seperate classes #48
Merged
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.
This PR refactors the model selection and handling logic by splitting the model manager into provider-specific classes, aiming to reduce complexity and improve modularity.
What’s changed
Created dedicated provider classes:
openai_provider.pyazure_openai_provider.pyanthropic_provider.pydeepseek_provider.pyIntroduced a
base.pywith a common provider interface (BaseProvider)Added a
registry.pyto dynamically resolve and initialize providersUpdated
model_manager.pyto delegate model usage to registered provider classes instead of conditionalsUpdated all references accordingly to use the new structure
Benefits
if/elseormatchlogic for provider selection