[ALERT] Fix for breaking changes introduced by Bearer Token work #121
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
aslisabanci
previously approved these changes
Dec 22, 2021
platypii
previously approved these changes
Dec 22, 2021
…d system handling no auth provided gracefully
aslisabanci
previously approved these changes
Dec 22, 2021
aslisabanci
approved these changes
Dec 22, 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.
the PR #116 introduced the concept of bearer tokens; but did not provide a mechanism for gracefully failing in the event that no API key is provided; this fix ensures that the bearer token is optional, and only attempted if a bearer token is provided.