refactor(RefreshTokenHandler): Send accessToken in Bearer Header for Refresh Token API and Fix Type Errors #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes Made
This PR updates the method of sending the
accessToken
to the refresh token API by including it in theAuthorization
bearer header. This change ensures better aligns with standard authentication practices.Additionally, default empty values were added to the id request parameters to prevent potential type errors. The status type in the
errorsHandler
was also updated toContentfulStatusCode
to improve type safety and ensure consistency with error handling.Changes Type
Checklist: