Added Rsvp rest api interestcount feature - #25
Open
huncijr wants to merge 3 commits into
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
1 participant
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 PR exposes the existing
toggle_user_interest()database logic as a publicPOST /api/rsvpREST endpoint, accepting{ event_id, user_id }and returning the updated interest state and count. When a user reacts to an RSVP message in Slack, theInterestedUsersarray updates and theInterestCountincrements; removing the reaction calls the same toggle logic and decrements the count. The updated count is also visible in the Slack Home tab for admins, and adds an interest badge on the Events website in events#82, where the frontend readsInterestCountfrom the existing read-only/events/API and displays it in the UI.hackclub/events#82
