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
Since the range salector gets put in a single Input, the range separator is localized in the format added and that could lead to errors when trying to parse out the date range in the back-end. The beta plugin that allows having two separate inputs solves this issue, but for the vanilla range input, that is a problem.
I suggest either adding an option to have a separate rangeFormat option + a range formatter token (ex.: r for localized, R for unlocalized English which defaults to "to")
{rangeFormat: "j M H:i R j M H:i"}
Would yield 22 Nov 4:20 to 22 Nov 4:21
{rangeFormat: "j M H:i r j M H:i"}
With French localization, would yield 22 Nov 4:20 au 22 Nov 4:21
With rangeFormat could be introduced altRangeFormat to follow what altFormat enables.
Your Environment
flatpickr version used: 4.6.13
Browser name and version: Safari 17.1
OS and version: Mac OS 14.1.1
The text was updated successfully, but these errors were encountered:
Hi,
Since the range salector gets put in a single Input, the range separator is localized in the format added and that could lead to errors when trying to parse out the date range in the back-end. The beta plugin that allows having two separate inputs solves this issue, but for the vanilla range input, that is a problem.
I suggest either adding an option to have a separate rangeFormat option + a range formatter token (ex.: r for localized, R for unlocalized English which defaults to "to")
Would yield 22 Nov 4:20 to 22 Nov 4:21
With French localization, would yield 22 Nov 4:20 au 22 Nov 4:21
With rangeFormat could be introduced altRangeFormat to follow what altFormat enables.
Your Environment
The text was updated successfully, but these errors were encountered: