Fix #4483: Enable onKeyDown handler for the month picker view and the year picker view #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
February 25, 2024 22:35
Used `handleOnMonthKeyDown` for MonthPicker component to handle Key down events as the `handleOnKeyDown` prop was linked with `handleOnDayKeyDown` (& passed to the Week component)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes Hacker0x01#4483
Description
This PR addresses the missing event handling to handle the key-press event for the month picker and the year picker. For the Year Picker component, I added
onKeyDownand mapped it to the corresponding prop. But, however the MonthPicker (month.jsx) is already receivingonKeyDownevent, but that was mapped to the handlerhandleOnDayKeyDownwhich is the handler specifically we're using onday.jsx. Inmonth.jsxwe're not directly using it, but passing that to theWeekcomponent. Hence for the month.jsx alone, I didn't change any of it's current behaviour, and I added a new prop namedhandleOnMonthKeyDownwhich is linked toonKeyDownevent handler we pass from the DatePicker component. So users can still useonKeyDownitself for any datepicker view (day/month/year), but internallymonth.jsxalone is handling it viahandleOnMonthKeyDown.Changes Made
onKeyDownevent.