[V2] Remove primitives and refactor MultiValue components #2821
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.
This primarily makes the
MultiValue{X}
components more consistent with the rest of the customisable components' APIs.MultiValueContainer
,MultiValueLabel
, andMultiValueRemove
all now receive the following props:data
- the option data for the value being displayedinnerProps
- as per other components, these are spread onto the dom componentselectProps
- passed from the outer Select component so functionality can be extendedThis should be sufficient to recreate the
onValueClick
behaviour in v1.Inspired by #2806