Chirag: Fixed user registration for activites#5138
Open
ChiragBellara wants to merge 3 commits intodevelopmentfrom
Open
Chirag: Fixed user registration for activites#5138ChiragBellara wants to merge 3 commits intodevelopmentfrom
ChiragBellara wants to merge 3 commits intodevelopmentfrom
Conversation
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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.



Description
Related PRS (if any):
This frontend PR is related to the OneCommunityGlobal/HGNRest#2152 backend PR.
Main changes explained:
How to test:
npm installandnpm run start:localto run this PR locally/communityportalScreenshots or videos of changes:
activity_registration_fix.mov
Note:
It is possible that the number of current attendees may not match the number of people listed in the Attendees list initially. That is because the registration API was just implemented and all the entries before that were done directly to the DB causing the calculation inconsistency on the UI. We need to flush the DB to resolve the inconsistency and that can be done once the changes an PR is approved.