You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last 2 events - the November and December events seem to have a problem. The "date" is a string in JSON - we convert this string into a Date object and sort on it (using a Date sort).
However, for some reason when passed to EventDetails - the date object isn't valid - and we get a runtime error.
Weirdly the event page that uses this same component + same JSON does not seem to be affected.
I also have not been able to reproduce this outside of the GitHub Action - making it very hard to debug.
I added a displayDate string as a workaround, and just catch the error and use displayDate if date does not work. But this is very hacky.
Actual
Would expect a date to be passed to eventDetails - and eventDetails to be able to parse and show said date.
Additional Info
When this fails it was bringing down the website :(
The text was updated successfully, but these errors were encountered:
Bug Report Checklist
main
branch of the repository.Expected
The last 2 events - the November and December events seem to have a problem. The "date" is a string in JSON - we convert this string into a Date object and sort on it (using a Date sort).
However, for some reason when passed to EventDetails - the date object isn't valid - and we get a runtime error.
Weirdly the event page that uses this same component + same JSON does not seem to be affected.
I also have not been able to reproduce this outside of the GitHub Action - making it very hard to debug.
I added a displayDate string as a workaround, and just catch the error and use displayDate if date does not work. But this is very hacky.
Actual
Would expect a date to be passed to eventDetails - and eventDetails to be able to parse and show said date.
Additional Info
When this fails it was bringing down the website :(
The text was updated successfully, but these errors were encountered: