[ADD] selectedDateState
as optional prop for DatePicker
to ease implementation when selectedDateState
is handled by ancestor
#5
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.
Add
selectedDateState
prop toDatePicker
andDatePickerProvider
to handleselectedDate
state from outsideDatePicker
component.The absence of
selectedDateState
keeps the previously defined behavior, it's entirely optional.This allows an easier implementation when
selectedDateState
is being handled by an ancestor component of theDatePicker
. For instance, you have a form with aDate
field and you need to provide the initial value based on fetched data. Putting thatDate
insideoptions
prop can get messy and lead to unnecessary rebuilds or inconsistencies.