-
-
Notifications
You must be signed in to change notification settings - Fork 66
[regression] "format" prop is gone from TimeInput #583
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
Comments
what version are you upgrading from? |
I assume you are upgrading from 0.12 which was based on Mantine V5 In Mantine V6 the In Mantine V8 (released a couple days ago), there is a new |
Yes, I'm upgrading from 0.12. |
Unfortunately it's not possible to add the format prop to the current version because the upstream Mantine component does not support it. I wish I had a better answer for you, but if that format prop is required, and you want to use a dmc component for the time input, it looks like the only option is to stay on dmc 0.12 or wait for dmc 2.0. You could see if anyone has published a dash timepicker as a separate component. Another option is to make your own custom dash component (at least to use until dmc 2 is released) I made one a few years ago: https://github.com/AnnMarieW/dash-more-components?tab=readme-ov-file#timepicker. It wraps https://github.com/wojtekmaj/react-time-picker |
Good news! I've started working on the PR for DMC V2 and making good progress. I'll try to prioritize adding the new TimePicker , but if you would like to help speed things up, I'd be delighted to get a PR for that component 🙂 |
This is great news indeed, thank you so much for working on this |
I just tried upgrading DMC in my environment and am getting this error when running my Dash app
Before upgrading the same code worked fine.
The code being like
As you can see, I set the
format
prop to"24"
to use the 24 hour format instead of the AM/PM one. But this property got lost at some point.This is important as people in my organization specifically requested the 24 hour format and we use it all over the place.
The text was updated successfully, but these errors were encountered: