react-dates: SingleDatePicker: No way to distinguish between invalid date and empty input

SingleDatePicker’s onDateChange handler is fired with null when user’s input doesn’t validate to a date. This can happen when the date is, in fact, invalid 13/13/2018 or when user input is empty.

Is there a way to tell these scenarios apart?

About this issue

Original URL
State: open
Created 6 years ago
Reactions: 46
Comments: 16 (1 by maintainers)

Most upvoted comments

We probably should make onDateChange fired with either a Date object or a string (contains whatever user’s original input) to fix this issue

t83714 on Dec 4, 2019

+1 this is driving me insane:)

Its probably a bug though, as onDateChanged should not be triggered at all. See README:

The SingleDatePicker also manages internal state for partial dates entered by typing (although onDateChange will not trigger until a date has been entered completely in that case).

JohnnyBDude on Dec 17, 2018

This is also tripping me up a little. My scenario is that I want to send a request to the server if the user “clears” the input, but I have no way of knowing if the null date arg was because of an actual clearing of the input or a temporary edit that put the input into an invalid state.

Perhaps additional arguments could be passed to the change handler, in addition to the date value? Something that refers to the validity of the current state of the input?

austenpayan on Sep 27, 2018

@viktoriyavulfson Did you ever find a solution to this issue?

charliedavison on Nov 25, 2019

Hi I checked the actual value of the input. I am not quite sure if I used document.getElementById or a ref to get the input

Flui on Jun 7, 2021