Date fields to only take date strings and not date objects

[anthony-dandrea]

Background

Mantine v8 introduced two relevant breaking changes:

1. Removing timezone support.
2. Making date fields onChange prop use a string instead of a Date object.

This removed a ton of timezone complexity on Mantine's side. However, these props still leverage DateValue which includes both the date string and date object:

• minDate
• maxDate
• value
• defaultValue

And I think the inconsistency can lead to confusing behavior. Especially for apps using Mantine that need to use a specific timezone that the user's machine isn't set to.

My Thoughts

I believe it'd be a more clear API if the date fields only accepted date strings. And never date objects for any of their props.

This sandbox illustrates the scenario and how it could bite someone. And the non-intuitive(IMO) steps needed to work around this use case.
https://codesandbox.io/p/devbox/mantine-date-minmax-repro-forked-jwrwpc?workspaceId=ws_9DEenomYG9hvRej8SwUPgy

Argument Against

• It would be a breaking change.
• I can workaround by overriding the types for my app myself.
• For Mantine consumers that only care about the user's current timezone, this could be worse DX.
  • Although, they already need to do translations for onChange so I don't think it's that bad.

Thanks!

I appreciate the work done on this library. It's been a real treat to use.