Closed romanstetsyk closed 1 year ago
Great idea!
what are your thoughts on loading events that are in the current month, visualizing, then loading events that are in prior and future months? I believe it should improve performance since most users are just looking at the current month anyways.
I agree. Loading events for the current month is a good idea. When the user scrolls to another month, only then load more events. The performance will improve as the application grows and more events are created. Also, there's no need to load events from previous months automatically. In any case, having some sort of spinner or skeleton would be nice.
I agree. Loading events for the current month is a good idea. When the user scrolls to another month, only then load more events. The performance will improve as the application grows and more events are created. Also, there's no need to load events from previous months automatically. In any case, having some sort of spinner or skeleton would be nice.
Yes I agree! I'll add an issue for loading.
I'll take a look at this!
Would it be a different issue to try and find a solution to optimize loading all events?
Would it be a different issue to try and find a solution to optimize loading all events?
@jmoldyvan there is issue #366 which might be relevant
I mocked up this "Shimmer" effect... it's a pretty common tactic. Something like this could go in the calendar day cards while waiting for the database to spool up.
Were ya'll thinking of doing something like this or something more unique?
I like this @intelagense
This is occurring on my desktop. @DevinCLane @Caleb-Cohen
good catch @intelagense, fixed it!
Please provide a summary of the feature
Sometimes it can take a while for all events to be fetched from the database. A loading indicator would be a nice feature.
Are there any potential issues you foresee with this feature
Is this feature related to any current or past issues? Please provide the
Additional context
Add any other context or screenshots about the feature request here.
Which Branch should this fix be Pulled into?
PR into
main
If you're interested in working on this feature, please comment so you can be assigned