-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat: 🎸 Component to force user date selection via DatePicker #80
Conversation
The SQFormDatePickerWithCalendarInputOnly component disables the text input forcing the user to make a date selection via the picker. Also allows the consumer of SQFormDatePicker the ability to disable any(s) in the calendar view. ✅ Closes: #74
@@ -61,9 +64,9 @@ function SQFormDatePicker({ | |||
{...inputProps} | |||
name={name} | |||
color="primary" | |||
disabled={isDisabled} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is redundant and doesn't do anything so removed it.
…oteLabs/SQForm into DatePicker_Enhancements
Nice work Sean, and thanks for providing examples. One non-blocker nit - might be good to mention in the proptypes that the setDisabledDate is just a predicate which every rendered day is checked against. Took me looking at your examples to understand how to use that. |
100% agreed. I'll commit this change |
🎉 This PR is included in version 2.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The SQFormDatePickerWithCalendarInputOnly component disables the text
input forcing the user to make a date selection via the picker. Also
allows the consumer of SQFormDatePicker the ability to disable any(s) in
the calendar view. See Issue 74 for more information.
Loom
The issue also unblocks AZT-1451 on the Senior CRM
✅ Closes: #74