Feature: Turning datepicker into a controlled component #4
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.
What kind of change does this PR introduce?
You can now use
onDateChange
andselected
props to control the datepicker, just like you would useonChange
andvalue
in an input element.Also, it adds a default prop to
firstDayOfWeek
and az-index
to the calendar component.What is the current behavior?
The
state
of the datepicker is not updated when a newselected
prop is provided.What is the new behavior?
When a new
selected
prop is provided, the datepicker recalculates its state.Checklist: