Open niccokunzmann opened 7 years ago
So i digged a bit, it's because they are sorted by creation date. The reason behind this is because with recurring event being stored as a single event, the process to sort an unique event based on the next occurence date is expensive. The best solution would be to have a view that I and Daniel thought about for quite some time, displaying only one row per event with the next date for this event as well as event info. This way we could use the normal filtering from seneca-entity which could solve this ordering issue.
Despite closing #1212, this one isn't yet as the API endpoint used is still the old one
If I look at the events list, I would like to see the events sorted by date. But: independently of how I sort them, February 4th is between two January events.
This is the current behavior:
Webpage: https://zen.coderdojo.com/dashboard/my-dojos/0be123e7-c9be-4002-a3cf-f0c8550f749a/events