Update the API class to properly put the access_token into the header. #535
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 pull request:
Api_new
class that mirrors the oldApi
class, butHttpRequest
, that includes headers information.This should be a non-breaking change at this point. I have run the existing tests, and they pass, but I did not try to improve test coverage; bugs could slip through the cracks.
The next steps would be to:
Api_new
->Api
, while having the oldApi
class available asApi_old
.Api_old
.Those will be braking changes for those, who depend directly on the Api class, but users will have a path to upgrade.