Add ability to override access token request headers #603
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.
This moves the currently hardcoded
getAccessTokenResponse
into their own method. This allows children providers to construct their own headers as needed.A perfect example of the necessity of this feature is the newer Pinterest v5 API. In order to exchange the code for an access token, they require an
Authorization
header composed of a base64 encodedclient_id
andclient_secret
. Without this change, the Pinterest Provider would need to entirely reimplement thegetAccessTokenResponse
method. With this change, the Pinterest Provider could simply: