-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FeatureRequest] Support nullable times #311
Comments
This seems to be an issue with the 24h format only. When closing the picker with 24 format enabled it throws this error. With the 12h format this does not seem to be a problem. Maybe it is a difference in the implementation of Edit: Looking at Luxon docs:
whereas
could this be the problem? |
I traced the problem to setting the default time when closing the picker when the format is 24h. I am however not sure why this occurs only for the 24h format. |
This bug is also present on the demo page |
@Nephyron which version do you use? |
Hey! I have the same issue, with the new version 5.4.3. |
* issue184: ! fix setting time without interaction with clock face * issue184: + add min and max time range * issue184: * move logic from defaultTime to updateTime * issue184: + condition to disable period selection * issue184: * change time after period changes * issue311: ! fix error that shows after closing timepicker without time changed in 24 format * issue184: ! prevent calling disableMinutes if selected hour is not provided * * update readme, changelog and version
Fixed in v5.5.0 |
Hello, |
Hi, ERROR in ../node_modules/ngx-material-timepicker/src/app/material-timepicker/components/ngx-material-timepicker-container/ngx-material-timepicker-container.component.d.ts:45:9 - error TS1086: An accessor cannot be declared in an ambient context. 45 set defaultTime(time: string); 46 get defaultTime(): string; 20 private get selectedTime(); 31 set format(value: number); 32 get format(): number; 33 set min(value: string | DateTime); How can I proceed further? Please let me know if you have any solution for this. |
@vignesh-balaguru use the latest version of the timepicker |
Do you guys know some workaround? |
When setting the timepicker value to null/undefined, instead of having the portion of code:
return parsedTime.toISOTime({
includeOffset: false,
suppressMilliseconds: true,
suppressSeconds: true
}).replace(/\u200E/g, '');
throw because cannot call .replace of "null" it would be nice to have the timepicker field reset to the placeholde "hh":"mm"
The text was updated successfully, but these errors were encountered: