refactor: rename output field from rationale to reasoning in MultiChainComparison #8955
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
…iChainComparison Updated the output field name for consistency with CoT. The extraction logic from completions remains unchanged: rationale = c.get(rationale, c.get(reasoning)).strip().split(n)[0].strip()
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.
Summary
Renames the output field rationale → reasoning for consistency with Chain-of-Thought (CoT) terminology.
No behavioral change to parsing logic; we continue to accept both keys during extraction to remain backward-compatible.
Changes
MultiChainComparison: output field renamed to reasoning.
Tests updated to use reasoning.
Extraction keeps accepting legacy rationale:
rationale = c.get("rationale", c.get("reasoning")).strip().split("\n")[0].strip()(unchanged logic; still prefers rationale if present, otherwise falls back to reasoning)
Motivation
Align naming with CoT and existing components that already use reasoning.
Reduce confusion between fields with the same semantic meaning.
#Backward Compatibility / Risk
Low. Callers reading only reasoning are supported; callers still sending rationale remain compatible via the fallback extraction.
External consumers relying strictly on the old key name may need to migrate, but the parser remains tolerant.