Allow GET requests to use tokens, if provided #5
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.
Some
GET
requests need to use tokens. Consider the following request:Before:
It'll return an error saying
Invalid parameter(s): status
After
It'll correctly return any draft posts
This PR addresses this by treating the presence of a valid
Bearer
token as an indication that the request should proceed as a logged-in user. If an invalidBearer
token is passed, the request proceeds as if it weren't present. This may be incorrect behaviour – we may wish to always treat the presence of a token, valid or not, as an indication that it's required.