fix(api): treat empty-string stop as omit no-op on chat/completions/responses - #550
fix(api): treat empty-string stop as omit no-op on chat/completions/responses#550seonghobae wants to merge 1 commit into
Conversation
…esponses Buyer SDKs often send stop:"" as an optional default meaning no stop sequences. Accept empty string as omit (parity with null and empty array) while still fail-closing non-empty Completions/chat stop and validating Responses stop shape. Tip honesty substrate re-ship; 832 unit pass.
|
Important Review skippedToo many files! This PR contains 115 files, which is 15 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (115)
You can disable this status message by setting the 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 |
Pull request was closed
Summary
Test plan
Product gates only: Full unit + Semgrep (Strix ignored). Independent non-author APPROVE still required.