fix(cli): handle None model.type in 'together models list' sort #257
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.
Sort key now uses 'x.type or ""' so models with type=None no longer cause TypeError when compared with str during sort.
Note
Low Risk
Small, localized change to CLI display sorting; behavior only differs when
.typeis missing, where it now avoids a runtime error.Overview
Fixes
together models listsorting to tolerate missing model types by usingx.type or ""as the sort key, preventing crashes when the API returnsNone/empty.typevalues.Written by Cursor Bugbot for commit 94bd7cc. This will update automatically on new commits. Configure here.