useHandle prop on SortableHOC example to prevent dragging on multiVal… #4387
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.
Update example for Sortable HOC
Issue reported: Sortable MultiSelect: Items are incorrectly deleted on touch device #4356
Description: When using the provided example, there are two distinct behaviors when dragging a
MultiValue
by theMultiValueRemove
component.Solution: These proposed changes updates the example so that it utilizes the
useHandle
prop on the SortableHOC to allow a handle to be wrapped around theMultiValueLabel
This should provide a more consistent experience of clearing the value instead of allowing it to operate as a draggable handle.
Working demo provided here: codesandbox