Pass API key when fetching individual exercises#307
Merged
Conversation
kytrinyx
force-pushed
the
auth-single-exercise
branch
from
96740dc to
8a244fd
Compare
Contributor
|
🎉 cool! |
kytrinyx
added a commit
to exercism/DEPRECATED.x-api
that referenced
this pull request
Apr 14, 2016
When someone fetches the next exercise (whichever it is) either across all their active tracks or in a specific track, we post back to the app so that we can show people their current status. When someone fetches an individual exercise, we weren't posting back. This fixes it for the individual fetch. This does presume that the CLI passes along the API key, which it originally was not doing. That's fixed in exercism/cli#307 and it will be a part of the 2.2.6 release.
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
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.
We're tracking what people fetch, and if we don't pass the key
we can't know who is fetching it.
Tangentially related to #303 and #305