-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Improve durations input format #3736
Comments
Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding! |
Hello there DuaelFr! 👋 Thank you and congratulations 🎉 for opening your very first issue in this project! 💖 In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀 For more open ended discussions and/or specific questions, please visit the discussions page. 💖 |
Problem Statement
In time estimates or time spent, we can input duration as a string instead of using the nice circular widget.
For example,
1h 45m
works just fine while1h45m
is calculated as1m
1h45
and guess it was 45 minutes1.5h
❔ Possible Solution
Improve
stringToMs
to:parseFloat
instead ofparseInt
None
➕ Additional context
Might help solve #3420 and #2983
The text was updated successfully, but these errors were encountered: