feat(adapter-openai-like): support additional request headers - #1037
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. Walkthrough配置新增 Changes自定义请求头
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Merge Risk: ⚪ Minimal · up to The added custom-header configuration is consistently passed into request construction, with no actionable merge risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
fd8527e to
511ced8
Compare
511ced8 to
c993022
Compare
Changes
additionHeadersoption to the openai-like adapter for custom request headers (e.g.x-opencode-session).Authorization,Content-Type,Cookie, etc.) are applied on top, so critical headers cannot be overridden.additionCookiesconcatenation: it was treated as an object although its type is[string, string][], which produced values like0=name,value; it is now mapped as tuples intokey=value; key2=value2.Verification
yarn fast-build adapter-openai-liketsc --noEmit -p packages/adapter-openai-like/tsconfig.jsonCloses #1035