Issue 1 – browser warning re non-conforming value in minute input when enableTime is set to true
Set the default minuteIncrement to 1, thus preventing the first issue descried.
Issue 2 – onChange handler not firing every time when value (time) changes
Add heuristic to determine a working default dateFormat depending on enableTime, enableSeconds, and noCalendar. As a result, users should never have to set a dateFormat themselves in order to have a working component. They are still free to set a custom date format that suits their needs.
Issue 3 – defaultHour and defaultMinute
Rename the story not raise wrong expectations, update/clarify the respective prop and story descriptions.
Closes #563.
Issue 1 – browser warning re non-conforming value in minute input when
enableTime
is set to true Set the defaultminuteIncrement
to 1, thus preventing the first issue descried.Issue 2 – onChange handler not firing every time when value (time) changes Add heuristic to determine a working default
dateFormat
depending onenableTime
,enableSeconds
, andnoCalendar
. As a result, users should never have to set adateFormat
themselves in order to have a working component. They are still free to set a custom date format that suits their needs.Issue 3 – defaultHour and defaultMinute Rename the story not raise wrong expectations, update/clarify the respective prop and story descriptions.