[WIP, Don't merge!] feat: POST /api/currency/get, a step currency backend #106
Conversation
This file contains 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
kevr
force-pushed
the
currency-backend
branch
from
8f67724 to
bc3515b
Compare
This route does a very simple thing: it converts the number of steps that a device has into a coin + badge value, and presents those currency values to the requesting user. It will also provide us a "single source of truth" when it comes to currency calculations for the application. In the front-end, this route should be used to obtain a server-side, up-to-date record of these gamified currencies. The value can then be cached in client state to deal with user interaction animations. Signed-off-by: Kevin Morris <[email protected]>
kevr
force-pushed
the
currency-backend
branch
from
bc3515b to
68dc44b
Compare
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.
This route does a very simple thing: it converts the number of steps that a device has into a coin + badge value, and presents those currency values to the requesting user.
It will also provide us a "single source of truth" when it comes to currency calculations for the application.
In the front-end, this route should be used to obtain a server-side, up-to-date record of these gamified currencies. The value can then be cached in client state to deal with user interaction animations.
Signed-off-by: Kevin Morris [email protected]