-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
enhancement(Datepicker) date range #549
enhancement(Datepicker) date range #549
Conversation
…mplemented input change handler for end date input; Fix issue where formatted date was not rendered correctly on date type input; Fix existing spec tests materializecss#360
…ange modal se lected option input validation
…d date input field creation on initialization
The merge-base changed after approval.
I will merge it in first, and then change the modal in #556 because date and timepicker depend on the modal component. We should change it to the Popover API since it is widely available in browsers now. https://caniuse.com/?search=popover |
The merge-base changed after approval.
As Ive been working on the #360 multi date select, I've found some additional issue's that I'm about to commit soon regarding date range select |
…day or multi day date selection; Implemented setDateFromInput for logical navigation within the calendar by mouse/keypress interaction on input change, fixes issue where calendar only navigated to latest changed field; Refactored handleCalendarClick, split up single date click and date range click for the sake of code readability and simplicity; Updated JSDoc, removed unused parameter; Deprecated _setToStartOfDay (function has no effect); materializecss#360
Ok, implemented additional refactoring based on my previous issues concerns, think this PR is ready for review Changelog as of the latest commits
|
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.
LGTM 👍
The merge-base changed after approval.
The merge-base changed after approval.
Proposed changes
Implemented date range select functionality as per pull-request #360
dateRange: true
is providedstyling of the in-range items needs to be addressed, propose create this in a new issue since the global layout of the datepicker is outdated: currently still follows the M2 guidelines
Types of changes
Checklist: