Datepicker: minDate is inclusive, maxDate is exclusive

[chrispymm]

This may not technically be a bug, but it is inconsistent and non-intuitive. The minDate and maxDate options to the datepicker component behave differently.

{{ mojDatePicker({
  id: "date",
  name: "date",
  label: {
      text: "Date"
  },
  hint: { 
    text: "For example, 17/5/2024."
  },
  value: "10/04/2025",
  minDate: "04/04/2025",
  maxDate: "21/4/2025"
}) }}

With the config above setting a mindate of 04/04/2025 and a maxDate of 21/4/2025

• 4/4/2025 will be disabled and non-selectable
• 20/4/2025 will be available for selection

It appears from the code in the component that the intention was for the minDate to be exclusive (as it uses < not <=) however a weird quirk of date comparison appears to be causing it to treat the provided minDate as excluded.

This would be a breaking change to fix