fix(useSortable): prevent from creating multi instances #3501
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.
Before submitting the PR, please make sure you do the following
fixes #123
).Description
fix #3496
prevent start multi instance
Additional context
🤖 Generated by Copilot at 9afb592
This pull request fixes a bug in
onClickOutside
and improves the performance and reliability ofuseSortable
. It ensures that theonClickOutside
function correctly handles null or undefined target elements, and that theuseSortable
function does not create duplicate Sortable instances.🤖 Generated by Copilot at 9afb592
onClickOutside
that caused incorrectshouldListen
value when target element was null or undefined (link)useSortable
by checking if one already exists for the target element (link)