Refresh MiniMax provider model example to MiniMax-M3 - #332
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe settings dialog updates MiniMax model ID, context limit, and variants JSON placeholders. Model discovery tests verify the updated metadata examples and use ChangesModel placeholder update
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Updated the MiniMax model editor examples to use the 1,000,000-token context and adaptive/disabled variants, and pushed a new commit. I ran the focused OpenCodeModelsEditor Vitest file, ESLint on the two changed files, and git diff --check. |
Reason: Refresh the user-facing MiniMax provider model example in the OpenCode model editor from the stale MiniMax-M2.7 to the current MiniMax-M3 model ID.
Updates the placeholder text shown in the Provider Model ID field of the OpenCode model editor dialog from
e.g., MiniMax-M2.7toe.g., MiniMax-M3, so the configuration guidance reflects the current MiniMax provider model. The matching test selector that locates this input is updated to keep the discovery test green.Actual checks:
MiniMax-M2.7placeholder reference remains in the touched files.Summary by CodeRabbit