Closed mradziwo closed 6 years ago
Yes, the error messages generated by voluptuous aren't perfect. :-)
Hi again,
Do you think allowing 7:4
instead of 7:04
makes sense as well? I've never seen such a format and would tend to not support it.
Best regards Robert
no, it has never occurred to me. Though H:MM:SS format is out from ISO 8601:2004 standard, it's widely used when manual typing of time is required and IEEE recommends or handling directly H:MM format or support entry manipulation to treat H:MM as 0H:MM. I could try to dig out the IEEE publication if you'd like it.
Best regards, Michał Radziwon
On 13 March 2018 at 08:03, Robert Schindler notifications@github.com wrote:
Hi again,
Do you think allowing 7:4 instead of 7:04 makes sense as well? I've never seen such a format and would tend to not support it.
Best regards Robert
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/efficiosoft/hass-apps/issues/9#issuecomment-372566609, or mute the thread https://github.com/notifications/unsubscribe-auth/AI1rE8fhZ8mFmDYKVbcPRvqO--HVs1xtks5td29FgaJpZM4Sl02W .
No thanks, I think the behaviour is fine now.
Thank you for reporting.
Best regards Robert
Providing a time without leading zero (e.g. 6:55 instead of 06:55) crashes the app with following - a bit misleading error.
I'd suggest to add H:MM handling. heaty v0.12.1