mirror of
https://github.com/MichMich/MagicMirror.git
synced 2025-06-27 03:39:55 +00:00
f6dcfb5ca3
This keeps relative dates accurate when the calendar's fetch frequency is much larger than a minute. As fetching incurs network traffic and load on servers and most calendars don't update that often, simply refreshing locally is enough. When using relative for today's events, dates will show as "in X minutes" or "ends in X minutes" for events within an hour and this goes out of date quickly. It's weird to see that the time is, say, 16:30 and an event that you know ends at 16:45 is shown to "ends in 23 minutes" because that's when the last fetch happened. Please forgive me if there's style issue, I don't have npm set up on my machine to run the formatter.