Allow user to override getToken
function.
#164
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.
Description
Allows the user to specify a custom function for retrieving the authorization token. Currently, the
getToken
function is fixed and the user is only able to use one of the pre-determined locations for their authorization tokens, such as theAuthorization
header.Now the developer can specify whatever location they desire. This is asked for in #147 and I need this as well.
This should not be a breaking change. I also tried to pass the opts object into the existing getToken function, but this approach seems the least intrusive and most configurable.
References
#147
Testing
Unit tests were added for this functionality. Should be verifiable with
npm test
. Tested on NodeJS v18.19.1, Ubuntu 24.04.Documentation
Documentation was updated with
npm run docs
, it led to more changes than I expected, but it seems to be from a commit hash reference changing.Checklist