Open
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
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.
Brief description
The UI Team lead Niko opened an issue last year regarding adding emotions to the backend API. This has now been implemented, unit tested and tested on Postman as well on this PR.
Change list
Added
PlayerEmotionenum and updatedPlayerSchemawith a history array.Implemented
GET /player/emotioncheckto let the client know if the daily popup is needed.Implemented
POST /player/emotionto record daily sentiment (limited to once per day).Fix: Resolved path alias issues in tests by switching to relative imports in the
Schema.Fix: Resolved controller routing collision by reordering static routes above dynamic parameters.
Fix: Aligned controller with
req.user.player_idto ensure correct database targeting.