chore(model): refresh MiniMax examples to current M3 flagship#892
Merged
Conversation
The model-name normalization utility advertises MiniMax as a recognized provider prefix via its JSDoc example and unit tests. Update those illustrative references to use the current M3 generation so docs and tests reflect the active flagship model, and drop the deprecated M2.5-highspeed example. Keep M2.7 coverage (still a supported alternative) and add a MiniMax-M3 case to verify the case-insensitive matcher still handles uppercase variants.
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.
Summary
Refresh the illustrative
MiniMaxreferences in the model normalization utility so the JSDoc example and unit tests track the current M3 generation rather than older M2.x examples.Changes
src/utils/model.ts: update theaddProviderPrefixJSDoc example fromminimax-m2.7tominimax-m3.tests/model-utils.test.ts: drop the deprecatedminimax-m2.5-highspeedcase, add coverage forminimax-m3andMiniMax-M3(verifies the case-insensitive matcher still handles uppercase variants), and keep the existingM2.7cases as a still-supported alternative.Why
The matcher itself does not need to change (the
^minimax-/iregex already handles any model in the family), but the advertised example and test fixtures had drifted to an older generation. Pointing them at M3 keeps the surface aligned with the current flagship and removes a deprecatedM2.5-highspeedreference.Testing
bun test tests/model-utils.test.ts-> 13 pass / 0 failbun test(full suite) -> 1395 pass / 0 failbun run release:validate-> ok