-
-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow scheme Property to Be Case-Insensitive in securitySchemeObjectToAuthObject Function #1816
Conversation
|
🦋 Changeset detectedLatest commit: b9e1b4b The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@shemsiu can scheme be in uppercase? |
It can, I see |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1816 +/- ##
=======================================
Coverage 57.23% 57.24%
=======================================
Files 191 191
Lines 25892 25890 -2
Branches 1958 1958
=======================================
Hits 14820 14820
+ Misses 11063 11061 -2
Partials 9 9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@hey-api/client-axios
@hey-api/client-fetch
@hey-api/client-next
@hey-api/client-nuxt
@hey-api/nuxt
@hey-api/openapi-ts
@hey-api/rollup-plugin
commit: |
Good catch, thank you @shemsiu |
This pull request introduces a change to the securitySchemeObjectToAuthObject function to allow the scheme property to be case-insensitive by converting it to lowercase. This ensures that the function can handle schemes provided in any case format (e.g., "Bearer", "bearer", "BEARER").