Skip to content
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

fix: auth scheme and token from client level #959 #960

Merged
merged 1 commit into from
Jan 23, 2025

Conversation

jeevatkm
Copy link
Member

fix #959

@jeevatkm jeevatkm added bug v2 For resty v2 labels Jan 22, 2025
@jeevatkm jeevatkm self-assigned this Jan 22, 2025
Copy link

codecov bot commented Jan 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.69%. Comparing base (7ad1178) to head (5316b6b).
Report is 1 commits behind head on v2.

Additional details and impacted files
@@           Coverage Diff           @@
##               v2     #960   +/-   ##
=======================================
  Coverage   95.69%   95.69%           
=======================================
  Files          14       14           
  Lines        2206     2207    +1     
=======================================
+ Hits         2111     2112    +1     
  Misses         71       71           
  Partials       24       24           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jeevatkm jeevatkm force-pushed the fix-client-level-token branch from dc7bf15 to 43db49c Compare January 22, 2025 06:00
@jeevatkm jeevatkm force-pushed the fix-client-level-token branch from 43db49c to 5316b6b Compare January 23, 2025 06:03
@jeevatkm jeevatkm merged commit aee0cb5 into v2 Jan 23, 2025
6 checks passed
@jeevatkm jeevatkm deleted the fix-client-level-token branch January 23, 2025 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug v2 For resty v2
Development

Successfully merging this pull request may close these issues.

Possible Authorization header bug in v2.16.4
1 participant