fix: expose rejectUnauthorized in RequestOptions - #919
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (5)
✨ 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 |
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #919 +/- ##
=======================================
Coverage 94.23% 94.23%
=======================================
Files 10 10
Lines 746 746
Branches 235 235
=======================================
Hits 703 703
Misses 40 40
Partials 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Callers cannot set
rejectUnauthorizedon an object typed asRequestOptions, although the top-levelrequest()andcurl()helpers already support it.Expose
rejectUnauthorized?: booleanthroughRequestOptionsand itsRequestOptions2alias. Both helpers use the public type. The documentation explains where the option applies and how to configure certificate verification forHttpClientinstances and custom dispatchers.Fixes #571.