fix: preserve insertion order for model variants in opencode API (fixes #145) - #311
Open
rohanranjan0902 wants to merge 1 commit into
Open
rohanranjan0902 wants to merge 1 commit into
rohanranjan0902 wants to merge 1 commit into
Conversation
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
1 participant
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.
Description
This PR fixes an issue where Codex model variants were being returned out of order in the OpenCode
/modelsAPI (e.g.["high", "low", "medium", "xhigh"]).Root Cause: The
opencode_compathandler manually builds the variants object, butserde_jsonusesBTreeMapby default, which inadvertently sorted the keys alphabetically during serialization.Changes:
preserve_orderfeature forserde_jsonin the workspaceCargo.toml. This swaps the underlying map implementation toIndexMap, preserving the logical insertion order defined by the agent configs.Fixes #145