How to use min/max for date fields?

The CMS Questions
1

Hello,

I try to set a min or max date for my blueprint date fields. To achieve this, I have defined this field:

  published:
    type: date
    required: true
    label: Published On
    min: 01.01.2019

The min (same with max) property is being ignored. I tried these formats (without the comma):

2019-01-01,
2019.01.01,
01.01.2019,
01-01-2019.

None of these values are respected if I choose some date in year 2018 and save the page. The invalid value is still valid and the javascript calendar to pick the date from provides invalid ranges. What am I missing here?

Best Regards

2

Hm, looks like a bug. While the dropdown doesn’t allow choosing anything below that date, the date picker does in fact allow you to choose any date.

1 Like
3

I checked the dropdown and it’s somehow wrong too: If you choose a date from 2018 and save it, then you can still select invalid dates from the dropdown. Only if you choose 2019, save and then open the dropdown again, only valid values are shown. Both is quite unlucky while the date picker is a bug and the partly wrong date dropdown is maybe bad usability.

What surprises me is that the value is indeed invalid (and the dropdown detects this) but you can still store invalid values - so there’s only a frontend and no backend validation.

4

I created an issue on GitHub:

Feel free to add your comments if something is missing.

1 Like
5

The issue is now closed on the dev branch and should then work as expected in the next release.

1 Like