You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://forum.primefaces.org/viewforum.php?f=57
Codesandbox Case (Bug Reports)
Please fork the codesandbox below and create a case demonstrating your bug report. Issues without a codesandbox have much less possibility to be reviewed.
Current behavior
The parseTime function throws an exception when props.showSeconds is false. This causes the user input not to be parsed to a Date.
Expected behavior
The parseTime works when props.showSeconds is false.
Minimal reproduction of the problem with instructions
Just create a Calendar with showTime="true" but showSeconds="false" and try to manually type a date time string in the input field. The bound date value will a string and not a Date because parsing fails.
Please tell us about your environment:
PrimeReact version:
3.1.3
The text was updated successfully, but these errors were encountered:
Mobe91
added a commit
to ordami/primereact
that referenced
this issue
May 25, 2019
I'm submitting a ... (check one with "x")
Codesandbox Case (Bug Reports)
Please fork the codesandbox below and create a case demonstrating your bug report. Issues without a codesandbox have much less possibility to be reviewed.
https://codesandbox.io/s/qjx332qq4
Current behavior
The
parseTime
function throws an exception whenprops.showSeconds
is false. This causes the user input not to be parsed to a Date.Expected behavior
The
parseTime
works whenprops.showSeconds
is false.Minimal reproduction of the problem with instructions
Just create a Calendar with showTime="true" but showSeconds="false" and try to manually type a date time string in the input field. The bound date value will a string and not a Date because parsing fails.
Please tell us about your environment:
3.1.3
The text was updated successfully, but these errors were encountered: