pass Authorization via msg.authorization #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Authorization header can now optionally be passed via msg.authorization field. Allows to get the authorization token from another source or a previous call instead of specifying it in the graphql connection.
|
Thanks for this PR! |
|
Thanks for integrating! |
|
Hey @rgstephens sorry to bother you, but do you know when this can be published? How can I help move this forward? Thanks! |
|
Just published! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Authorization header can now optionally be passed via msg.authorization field. Allows to get the authorization token from another source or a previous call instead of specifying it in the graphql connection.
In my case i have to do a graphql call with user/pass to gain the token and then pass this one in the other calls.
Would be really great if you could add that to your branch and update the npm package. Thanks a lot.