-
Notifications
You must be signed in to change notification settings - Fork 126
feat: add --search flag to filter models (#128)
#157
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.
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doing a local search could match descriptions at near-zero extra cost.
Remote search matches name + description, but local matches name only. That asymmetry is fine and it's documented in the help text, so this isn't a bug. Just noting that the usual reason to skip description matching here. Having to load + parse each model's JSON doesn't actually apply: the display loop below already calls
load_model_info(model[:path])for every model (line 443) to read its type. The JSON is parsed regardless.So searching descriptions locally wouldn't add the I/O it appears to. One option is to load info once per model up front, then filter on both name and
info['description'], reusing the same parsed hash for display.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cardmagic Am I correct in understanding that search by description for local models may be added in the future? That is, for new models, their description will be added to the JSON file.
Fixed, check, please.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You've got it right. The cached local files are raw classifier dumps — they carry
typebut nodescription(that only lives in the registry'smodels.json), so local--searchmatches on name for every model today. Your preload approach is forward-compatible: if a model file ever includes adescriptionkey, local search picks it up for free since we already parse each file for thetypecolumn.