[Feat] Enable temporal selector `DatePicker`

[nadijagraca]

Description

Added temporal selector DatePicker for Filter and Parameter.

DatePicker is a single model, but based on value of argument range will either return dmc.DatePicker or dmc.DateRangePicker. Default value of range is True and the model will return dmc.DateRangePicker if range is not provided, or if the selector is not defined.

Options where DateRangePicker is returned:

1. User does not define the Filter.selector but filter column is datetime dtype.
2. User defines vm.DatePicker as Filter.selector without specifying range argument or by setting range=True

Option where DatePicker is returned:

1. User defines vm.DatePicker as Filter.selector and sets vm.DatePicker range argument as False.

vm.DatePicker.value supported format are all inputs that could be translated to datetime.date. See more here

Done is separate pr:

• [x] styling
• [x] docs
• [x] tests

Screenshot

---

---

Notice

• [x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

  • I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
  • I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
  • I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
  • I have not referenced individuals, products or companies in any commits, directly or indirectly.
  • I have not added data or restricted code in any commits, directly or indirectly.

[antonymilne]

This looks great! Just some answers to your open questions and then I will do a full review next week 🙂

• How to hand value argument in both date picker and date range picker? I followed the approach of slider and range_slider in this pr, meaning if value is not provided I take min_date allowed for date picker, and [min_date, max_date] for date range picker.

This sounds right to me 👍

• Do we keep min_date/max_date or do we replace it with min and max as in sliders?

Let's go for min and max to match the sliders.

• Do we need to add more arguments to the components? I kept it minimal, but some of the additional args to add could be: allowFreeInput, clearable etc. For more information about possible args check: https://www.dash-mantine-components.com/components/datepicker

Definitely keep it minimal and just expose only the essential arguments like we do for slider/rangeslider. What we should do though is set values for these fields if we think the dmc defaults aren't suitable for us. But those wouldn't be configurable as model fields, just hardcoded into the component returned in the build method.

[AnnMarieW]

Be sure to set the dropdownPosition prop. It seems to be a workaround for this issue: https://github.com/snehilvj/dash-mantine-components/issues/219

[huong-li-nguyen]

@nadijagraca - let us know how it goes! I found several issues regarding the datepickerrange from the mantine library that are still open, all concerning persistence.. So if this is not easy to solve, then let's brainstorm next week what alternatives we have. As Petar said, I also hope that we find a way to fix this other than replacing it with the dcc version 😅 I think even if we would replace it with the dcc version, it should be straight-forward except for the styling 😓 But let's see!

If you haven't seen it yet:

• https://github.com/snehilvj/dash-mantine-components/issues/212
• https://github.com/snehilvj/dash-mantine-components/issues/185