fix: access on-search-change with correct path - #933
Closed
ullasgowda wants to merge 1 commit into
Closed
Conversation
Author
|
My initial understanding of the issue was incorrect, so this PR doesn't address the actual problem. I'm closing this PR. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related Issue
#932
Description
This helps fixing onSearchChange. Currently onSearchOption never gets invoked as it is referenced from the wrong object.
Impacted Areas in Application
List general components of the application that this PR will affect:
Additional Notes
I wanted to handle a specific use case triggered by a change in the search text, but I noticed that it isn’t working in the current version. While looking into the code, I identified the root cause and wanted to help fix it.