You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Small feature request: The CupertinoDatePicker underlying DateTimeAnswerFormat supports "minimum date" and "maximum date" arguments that make it so the selected date must be within certain boundaries (there are also minimum year and maximum year arguments that just do this for year, but these are just simplified versions of the minimum and maximum date arguments that take ints instead of datetime objects). It would be helpful if these could be used as optional arguments in the DateTimeAnswerFormat constructor, as it would save the trouble of validating responses after the fact when the date/time needs to be constrained in some way.
The text was updated successfully, but these errors were encountered:
Small feature request: The CupertinoDatePicker underlying DateTimeAnswerFormat supports "minimum date" and "maximum date" arguments that make it so the selected date must be within certain boundaries (there are also minimum year and maximum year arguments that just do this for year, but these are just simplified versions of the minimum and maximum date arguments that take ints instead of datetime objects). It would be helpful if these could be used as optional arguments in the DateTimeAnswerFormat constructor, as it would save the trouble of validating responses after the fact when the date/time needs to be constrained in some way.
The text was updated successfully, but these errors were encountered: