Chirag - Fix Event fetch error on the Community Calendar Screen#5241
Open
ChiragBellara wants to merge 6 commits into
Open
Chirag - Fix Event fetch error on the Community Calendar Screen#5241ChiragBellara wants to merge 6 commits into
ChiragBellara wants to merge 6 commits into
Conversation
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ChiragBellara
added
the
High Priority - Please Review First
…ps://github.com/OneCommunityGlobal/HighestGoodNetworkApp into chirag-fix-event-fetch-error-on-calendar-screen
|
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.
Description
Related PRS (if any):
This frontend PR is related to OneCommunityGlobal/HGNRest#2198
Main changes explained:
How to test:
npm installandnpm run start:localto run this PR locally/communityportal/calendarScreenshots or videos of changes:
FixCommunityCalendarEventDisplay.mov
Note:
This screen can still produce duplicate-entry behavior for certain dates because some legacy records in MongoDB contain multiple rows/documents with the same ID. When switching dates, the UI cleanup logic removes only one instance of the duplicated ID, leaving stale entries behind and causing console errors.
This is caused by pre-existing corrupted/duplicate data and is not introduced by this PR. The underlying database issue no longer occurs for newly created records, but historical data has not yet been cleaned up.
A proper fix would require a MongoDB data cleanup/migration to remove duplicate records.