Initially setting a null dateTime breaks the datepicker

[leoasis]

Setting a null value initially for the datepicker (or an empty string for that matter) breaks the datepicker. If it is passed a null value, the calendar isn't even shown and there is a NaN title. If passed an empty string, the calendar is shown, but the internal state's selectedDate is invalid, and since every new value is cloned from it, all further values are invalid and the onChange always returns an "invalid date" string.

It would be nice to support a null value in the DateTimeField since sometimes in forms the dates are optional.

[Yuripetusko]

+1 I would like this also

[edy]

to empty the input field you have to set an empty default text (see #69): defaultText=""

[jbroadice]

Here's a workaround for this issue:

<DateTimeField
  inputFormat={ humanDateTimeFormat }
  onChange={ this.onDateTimeChange }
  defaultText={ this.state.date ? moment(this.state.date, 'x').format(humanDateTimeFormat) : '' }
  dateTime={ this.state.date || undefined }
/>

[jozan]

I'd like to see this issue getting fixed. Optional input fields are quite common usecase.

🐤

[bdittmer]

I'd love to see this get addressed too...

[nunogoncalves]

+1 here! Me too.

[throoze]

👍 +1 here. As @jozan says, this is a very common usecase, especially with dynamically generated forms.

[slangeberg]

👍 +1 from me - pretty sure it's messing us up in Redux app.

However, suggestion above does not work for me - 👎 I get broken calendar, if i supply defaultText, but dateTime is undefined.