Add support for Token field to enable v3 token authentication #187
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
ncw
approved these changes
Jun 2, 2025
Owner
ncw
left a comment
ncw
left a comment
There was a problem hiding this comment.
That seems very sensible - thank you.
Author
|
@ncw Thank you for your "swift" response! |
Author
|
@ncw Hi! Would it be possible to create a new release that includes the changes from this PR?. Thanks! |
Owner
|
Done - thanks @dkokkino |
Author
|
@ncw Thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 adds a new
Tokenfield to explicitly support v3 token authentication, improving clarity by separating it from the existingApiKeyusage. The existing behavior withApiKeyremains unchanged for backward compatibility.