-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: update option list search logic to handle string and array form_data values #2701
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 code looks generally correct, but there are a few things to consider for optimization:
Code Style: The use of
constfor local variables is good practice. However, TypeScript types should be explicitly defined when using optional chaining (?.) because it can sometimes lead to unexpectedundefinedvalues.Type Checking: Ensure that the types of inputs to your function and methods are correctly handled. If
'string'is expected and you want more complex string matching logic (e.g., substring search), this could benefit from additional type checks or functions likeString.includes.Performance Considerations: Since your current implementation iterates over all options to find a match based on a single criteria, this might not scale well with large lists. Consider sorting the list or creating an index if possible.
Functionality Clarification: Currently, if no match is found, the returned object will be empty
{}. For users expecting some indication, you might want to add logging or display messages indicating that no valid option was found.Based on these points, here's a slightly improved version:
This version adds basic functionality around indexing, which can improve performance. It also includes error handling for undefined indexes in case
indexOfreturns-1.