feat(APIRequest): support setting global headers in HTTPOptions #5586
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
kyranet
approved these changes
May 4, 2021
kyranet
previously requested changes
May 4, 2021
Co-authored-by: Vlad Frangu <[email protected]>
iCrawl
approved these changes
May 6, 2021
kyranet
approved these changes
May 6, 2021
SpaceEEC
approved these changes
May 9, 2021
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.
Please describe the changes this PR makes and why it should be merged:
Adds support for setting ClientOptions#http#headers to an object of headers which will be set on all API requests.
This is useful for using the canary API, setting a global audit log reason, and maybe other stuff in the future
The unrelated typings changes seem to have been automatically done by commit hooks
Status and versioning classification:
(commitlint didn't like naming the scope
APIRequest)