Disable specific dates and support ranges

[melohagan]

Description

Attempting to solve this use-case: #8402
When you want to allow users to choose a Start and End date, but not allow them to create a range that intersects disabled dates.

Disabled dates

Consider a table with holidays that you want to disable from the date picker calendar:

You can use the Disabled dates field to disable these dates. In this case the following handlebars expression is being used: {{ pluck DisabledDates Data Provider.Rows 'Holiday' }}

Date range

There was some code already in here to handle a little bit of the flatpickr range mode, however I wasn't able to find anywhere that actually used it, but if there is some other use of the functionality I need to test then let me know!

Added a check box for Range mode. When ticked, you can select a date field as the To (end) date.

This is probably a bit unorthodox as it involves registering two form fields in one component, but here's an example form:

Unticking the range mode will revert to using the Start date only.

Addresses:

• Allow disabling of specific dates in Date Picker #8415

App Export

Date Picker Range-export.tar.gz

[mike12345567]

Hey @melohagan had a look through this - I think its an important change but I'm not sure this is the correct way to go about it. We've a relatively large dependence on flatpickr right now - which we don't like - this will increase our dependency on the package and make it harder to replace.

I also think from our technical point of view breaking this out into a separate component, so we have a Date Picker and a Range Picker would be preferable - I had a chat with @aptkingston about this - there already is a component we use in the builder, it would just need to be exposed to the client library.

Going to close this for now as I think we'll need to think further about this - the date picker is already quite problematic and I wouldn't want to worsen the issue.

[melohagan]

Hey @melohagan had a look through this - I think its an important change but I'm not sure this is the correct way to go about it. We've a relatively large dependence on flatpickr right now - which we don't like - this will increase our dependency on the package and make it harder to replace.

I also think from our technical point of view breaking this out into a separate component, so we have a Date Picker and a Range Picker would be preferable - I had a chat with @aptkingston about this - there already is a component we use in the builder, it would just need to be exposed to the client library.

Going to close this for now as I think we'll need to think further about this - the date picker is already quite problematic and I wouldn't want to worsen the issue.

That's fair - thanks for having a look!