-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Remove unnecessary PromiseEmitter. #19845
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
Conversation
💚 Build Succeeded |
|
I appreciate that this will simplify the SearchSource, but can you please verify that nothing is using PromiseEmitter before removing it? If you did, please include details like that in the description. |
|
Also, by using PromiseEmitter, I more mean relying on the fact that handlers for methods like |
|
Thanks @spalger! Done. |
spalger
left a comment
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.
LGTM! Checked queries in discover, visualize, dashboard, and updates on filter and time range.
Good catch and thanks for doing this. Any opportunity to rip complexity out of the courier is an opportunity we should take.
jen-huang
left a comment
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.
LGTM! Verified that there aren't any other usages of PromiseEmitter or passing a handler to onResults.
This slightly simplifies the way SearchSource works. I've verified that nothing uses PromiseEmitter or passes a handler to
onResultsby grepping the codebase and waiting for CI to pass.