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
Currently, the date and time in the calendar is formatted on the the basis of the calendar-locale property. It would be nice to be able to handle language, date format and time format using separate properties. Perhaps with date and time format falling back to locale when these properties are not set.
The text was updated successfully, but these errors were encountered:
Okay, agreed there should be a way to customize labels, but there are definitely some challenges in doing so. Most of the labels use Luxon (the underlying date class we're using) to handle formatting. It should be pretty easy to have an object that has a named label and the accompanying Luxon code we want to use. Those functions should run through the function called formatDate() so we can just add the functionality there.
The issue I see is where we are dynamically creating "smart" labels dependent on the content. So take a label for a 5 day calendar. It might be labelled December 15-19 for days in the same month, or December 30 - January 3 if it crosses a month. We'll have to have a crafty way of dealing with those situations.
Currently, the date and time in the calendar is formatted on the the basis of the
calendar-locale
property. It would be nice to be able to handle language, date format and time format using separate properties. Perhaps with date and time format falling back to locale when these properties are not set.The text was updated successfully, but these errors were encountered: