feat: improve model name resolution flexibility#65
Merged
Conversation
Support slash separator (argo/gpt-4o), case-insensitive matching, and automatic argo: prefix handling for more flexible model resolution. Co-authored-by: Murat Keceli <keceli@gmail.com>
Remove redundant argo: prefix stripping (values use compact format like gpt4o, not hyphenated gpt-4o). Add comments explaining the alias key format and why each candidate transformation exists.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ported from @keceli's fork (https://github.com/keceli/argo-proxy).
Changes
_model_lookup_candidates()method toModelRegistryfor flexible model name matchingargo/gpt-4o→argo:gpt-4o)argo:prefix handling (add/remove as needed)test/test_model_resolution.pywith comprehensive test coverageCredit: @keceli