feat: custom headers support#59
Merged
Merged
Conversation
This file contains hidden or 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
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.
Pull Request
Description:
Add support for passing arbitrary custom headers when constructing a
Connection, bringing the Node SDK to parity withvideodb-python's**kwargs→x-*header behavior.Changes:
HttpClientaccepts a new optional 3rd argumentoptions?: HttpClientOptionswith aheadersfield; entries are auto-formatted tox-kebab-caseand merged into the axios instance defaults alongsidex-access-tokenandx-videodb-client.Connection(and the innerVdbHttpClient) forward the newoptionsargument through toHttpClient.connect({ ... })accepts a top-levelheadersfield onConnectionConfigand forwards it asoptions.headersto the newConnectionsignature.connect(apiKey, baseUrl)positional signature is unchanged.Related Issues:
Checklist: