-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Watcher] Retain query in watcher list #163297
Conversation
@elasticmachine merge upstream |
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
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.
Thanks for patching this up @sabarasaba! Left one comment about surfacing the error message.
@@ -446,7 +449,15 @@ export const WatchListPage = () => { | |||
: '', | |||
}; | |||
|
|||
const handleOnChange = ({ queryText, error: queryError }: EuiSearchBarOnChangeArgs) => { | |||
if (!queryError) { |
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.
Should we surface an error message if there is an error? Otherwise, it might not be clear to the user why a particular search returned no results.
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.
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.
Latest LGTM. Thanks @sabarasaba!
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @sabarasaba |
Summary
When working on #162687 we changed the table search to be controlled by the component it self. But as a side effect, the auto-refresh from the table clears up the query after x amount of time. We didnt caught this back then because the test that checks that was disabled and we only figured out after we tried to re-enable them with #162592.
This PR's patches it up so that we retain the query only when we dont have any errors.