FR: Granular control over date/time pickers.
See original GitHub issueIt would nice to have the below features in the picker:
- Allow Custom header messages (useful when there are multiple pickers with autoOK)
- Make action buttons optional, again useful with multiple pickers.
- All custom defined,
onTouchTap
events for action buttons.
Let me if this sounds ok, ready to do a PR.
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
mui/material-ui - FR: Granular control over date/time pickers.
Alright, say the user has to pick two dates from two different date pickers in the same page, it would nice to have...
Read more >Pickers - Selection and input - Human Interface Guidelines
A date picker is an efficient interface for selecting a specific date, time, or both, using touch, a keyboard, or a pointing device....
Read more >Date and Time Pickers for All - React Spectrum Libraries
We are very excited to announce the release of the React Aria and React Spectrum date and time picker components! This includes a...
Read more >Class: DateTimePicker - Salient Process
The Date Picker control allows for the specification of a date (only, no time) thru an entry field or a Calendar widget. A...
Read more >Is there a TIME PICKER? - Power Platform Community
I have a datepicker that I use for filtering my results. The results' datasource is the Case entity at the CDS. Right now...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hemanth Closing this for now. The custom header wouldn’t work with a landscape dialog, the button labels can be customised, and hooks for the buttons isn’t something we want to add.
@hemanth The edge cases are so many. and this use-case is so specific. If we make actions customizabe then how far should be expose them? we’ll end up with date-picker having a huge number of prop. if we provide an actions prop so the user can provide the buttons then how will we hook the OK and CANCEL with them? this will lead to a very un-intuitive API. Maybe it’s best to provide ways for users of this library to build their own date-picker the way they want. By exposing all date-picker components and customization guild. @oliviertassinari What do you think?