WP-379: Error handling for site search results #925
Merged
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.
Overview
In site search, involves 3 things:
When community data file search fails because user does not have access to community, the entire site-search fails. This PR addresses that. It allows user to see the other site search results, when public and community data files search files with specific tapis errors.
Related
Changes
Testing
Local testing pre-req: Setup search
Tested site search with authenticated user (no regression)

Tested site search without authenticated user (no regression)

The above two scenarios still do not hit the use case this PR is fixing. New unit tests are written to force tapis error and check the response.
For pprd and prod scenario, use a2cps site search to validate this PR.
UI
Notes