This repository has been archived by the owner on Dec 30, 2022. It is now read-only.
fix(connectRange): update default refinement propTypes #978
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.
Summary
Fix #564
With the current implementation when we provide a
defaultRefinement
toconnectRange
we must pass an object with bothmin
&max
. There are some cases when we want to pass only a min, max or even an empty object. In the latter case it allow the widget to be "controlled" by thedefaultRefinement
. See #892.