🐛 Bug: slice() error in Upcoming Events when results is undefined + unclear empty state #265
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
This PR fixes the
sliceerror in the Upcoming Events section and improves the empty state UI.Closes #264
Changes Made
Array.isArray(topEvents?.results)before calling.slice().CalendarXicon with a descriptive message.Before:
resultswasundefined.After:
How to Test
OurEventsis rendered.Checklist
Closes #264)Additional Notes
This fix improves both stability (no crashes when data is missing) and user experience (clear empty state).