-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: Form collection, multiple dragging and dropping of parameters failed(#3745) #3874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The provided code looks largely correct, but there are a few suggestions and improvements to consider:
Cloning
form_data.value.form_field_list:Since you're modifying an array directly (which can lead to unintended side effects), cloning it before performing operations is generally a good practice. However, this might be more relevant within the context of larger applications where multiple components might access the same data.
Using
map()for Array Operations:The current implementation uses
filter, which creates a new filtered list instead of modifying the original. If you intend to perform modifications that change the order or remove elements, usingmap()would better fit the intent.Consistent Variable Naming:
Ensure variable names like
items.oldIndex,movedItem`, etc., are consistent with standard naming conventions.Handling Edge Cases:
Consider adding checks to ensure that
evt.oldIndexandevt.newIndexfall within valid bounds.Here's a refined version of the code incorporating these suggestions:
These changes should help improve readability and robustness, especially in larger-scale projects.