[pickers] DateTime.fromISO() is not handling null values

[Arkamit]

[pickers] DateTime.fromISO() is not handling null values

[flaviendelangle]

What you are describing is the behavior from Luxon.
DateTime.fromISO(value) returns an invalid date, so when you pass it to the picker, we display an error.

I would advise you to always store a Luxon object in state, not an ISO string.
Because right now, you are storing an ISO string, parsing it with fromISO and then storing a Luxon object, that will be parsed with DateTime.fromISO, this works but it's super weird and goes against Luxon types.

---

Or if you really need an ISO string, they check if it is null and if so pass null to the picker

const parsedValue = React.useMemo(() => value == null ? value : DateTime.fromISO(value), [value])

In which case you need to stringify it back in your change handler to actually store a string.

[Arkamit]

@flaviendelangle Thanks for your suggestion. Adding a null check does work. I was just confused with the fact that when we add some month or day and then remove everything, the value becomes null again but this time it doesn't throw the error and reason comes as null instead of invalidDate which is a bit weird. Unfortunately I couldn't find any examples of initializing a datepicker with null or empty values for luxon adapter as well.

[flaviendelangle]

Unfortunately I couldn't find any examples of initializing a datepicker with null or empty values for luxon adapter as well.

These behaviors are not specific to Luxon.
For any adapter, null is the value when no date is selected, whereas the invalid date (in the format of your date library) represents an invalid date.

If you are still doing fromISO even with the null check, could you tell me why you are not storing the parsed object in state instead of parsing it during the render ?

---

when we add some month or day and then remove everything, the value becomes null again but this time it doesn't throw the error and reason comes as null instead of invalidDate which is a bit weird.

I did not understand that part, could you please describe more in depth?
When you remove all the sections, the value is null so we fire onChange with null not with an invalid date.
Our components almost never fires an invalid date, the only reason I can see is if you type something like 31 April.

[Arkamit]

When you remove all the sections, the value is null so we fire onChange with null not with an invalid date.
Our components almost never fires an invalid date, the only reason I can see is if you type something like 31 April.

This answers my question. I'm now using the null check for the initialization. Thanks for your help.