DRYD-1259: Fix repeated search panel requests when login has expired. #187
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.
What does this do?
This correctly connects the
searchError
prop of theSearchPanel
component to state from the Redux store. Previously,searchError
was not being set, even though it was needed for proper functioning of theSearchPanel
. It also tweaks the conditions under whichSearchPanel
executes a new search.Why are we doing this? (with JIRA link)
This fixes a bug where the
SearchPanel
would issue a new search whenever a search resulted in an error. When the error was a 401 due to not being logged in, this would cause an endless loop of searches.JIRA: https://collectionspace.atlassian.net/browse/DRYD-1259
How should this be tested? Do these changes have associated tests?
Expect: A single request is made to populate the Reports sidebar, and another single request is made to populate the Data Updates (batch) sidebar. The requests should return 401 errors. The requests should not be repeated after the 401 errors.
Dependencies for merging? Releasing to production?
None.
Has the application documentation been updated for these changes?
n/a
Did someone actually run this code to verify it works?
@ray-lee ran this locally.