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
{{ message }}
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.
I know that this topic has been mentioned/discussed e.g. in #3 and #22 but I'd like to reiterate that from a dev/user perspective, it is not obvious that the formatRange() result will be automatically extended to more than the date fields specified in the options. Especially since the normal format() function behavior only returns the fields specified in the format options (because no field extension needed for obvious reasons).
While I'd love to see this to be the default behavior (collapse to the specified date fields), I understand that changing it at this stage would bring more confusion than have benefit. However I really would like to emphasise the need for at least an additional option field to define to either ignore all unspecified date fields or collapse to a given date field.
Examples were mentioned in the issues listed above but include e.g.: 10 PM - 6 AM Dec 1 - Jan 1
I am currently forced to build those date ranges myself as I cannot use formatRange() to handle those ranges correctly/properly for my use case.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I know that this topic has been mentioned/discussed e.g. in #3 and #22 but I'd like to reiterate that from a dev/user perspective, it is not obvious that the
formatRange()
result will be automatically extended to more than the date fields specified in the options. Especially since the normalformat()
function behavior only returns the fields specified in the format options (because no field extension needed for obvious reasons).While I'd love to see this to be the default behavior (collapse to the specified date fields), I understand that changing it at this stage would bring more confusion than have benefit. However I really would like to emphasise the need for at least an additional option field to define to either ignore all unspecified date fields or collapse to a given date field.
Examples were mentioned in the issues listed above but include e.g.:
10 PM - 6 AM
Dec 1 - Jan 1
I am currently forced to build those date ranges myself as I cannot use
formatRange()
to handle those ranges correctly/properly for my use case.The text was updated successfully, but these errors were encountered: