FIX: recurring events not displayed on /upcoming-events #676
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.
When we introduced the
DiscoursePostEventEvent
model and the API service, the recurrent events stopped working as their logic still relied on the old naming convention,upcoming_dates
.This PR changes the
addRecurrentEvents
logic to work with and to createDiscoursePostEventEvent
s for each of theupcomingDates
, and changes the logic on the Category calendar to also work with theDiscoursePostEventEvent
instance instead of the plain object, as well as re-using the API service to fetch the events.The function passed to
onPageChange
was also changed toasync
/await
with some minor changes for clarity.