Repository navigation
fix(app): ignore none-only reasoning variants in tooltip - #1
Conversation
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
@zhengkaics A GitHub Actions policy edge case is blocking the I checked the inherited So this is a workflow-rule mismatch, not an unreported bug. Please merge the 2-file stacked PR into your feature branch (or cherry-pick Verification: original 4/5 tests, corrected 5/5, only two files changed, and GitHub shows this PR as mergeable. |
029af99
into
zhengkaics:model-reasoning-capability-v2
Issue for this PR
Fixes anomalyco#53520 (together with the parent PR anomalyco#55100). Also related: anomalyco#50257.
Type of change
What does this PR do?
This PR targets the head branch of anomalyco#55100, not OpenCode
dev.The reasoning tooltip fallback introduced by anomalyco#55100 treats every nonempty variants array as proof of reasoning support. An array containing only
noneinstead represents the ability to disable reasoning; it should not report "Reasoning supported".Replace
model.variants.length > 0withmodel.variants.some((variant) => variant.id !== "none"). Preserve the catalog's explicit reasoning flag and the existingreasoningFieldfallback. Add regression fixtures fornonealone andnone+high.How did you verify your code works?
git diff --check: pass. Compared with fix(core): expose model reasoning capability anomalyco/opencode#55100's head; only two files differ.Screenshots / recordings
Not applicable to this metadata-only refinement; no patched desktop build available. Test cases demonstrate the changed tooltip value.
Checklist