-
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
[Monitoring] remove imports from the legacy 'elasticsearch' package #106955
[Monitoring] remove imports from the legacy 'elasticsearch' package #106955
Conversation
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 overall. Curious about that !
usage though. Maybe just a learning moment for me.
@matschaffer |
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! so sounds like you can opt to use non-null assertion when the response will definitely include a _source
based on the request that it started with.
Seems like a good PR to me then. If tests agree, I'd say let's merge it.
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
…lastic#106955) * do not import types from the legacy es package * adjust tests
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…lastic#106955) * do not import types from the legacy es package * adjust tests
Summary
Use types and
error helpers
from@elatic/elasticsearch
package