-
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
[Lens] unify expression search context type #172738
[Lens] unify expression search context type #172738
Conversation
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
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.
Any removal of the SerializableRecord type looks good in my book! Type changes only for the Presentation team - so code only review!
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! Code review only
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.
Code-only review. Data Discovery type changes LGTM 👍
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
## Summary While working on elastic#172710 I noticed how loose our search context types were. This leeway seems like overkill given how we actually use the expressions framework. --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit 570937f)
# Backport This will backport the following commits from `main` to `8.12`: - [[Lens] unify expression search context type (#172738)](#172738) This is a prerequisite to backporting #172710 <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Drew Tate","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-12-11T14:08:00Z","message":"[Lens] unify expression search context type (#172738)\n\n## Summary\r\n\r\nWhile working on #172710 I noticed\r\nhow loose our search context types were. This leeway seems like overkill\r\ngiven how we actually use the expressions framework.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"570937ff19c500d0d54b605b0602b6ffb2a6fb10","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:ExpressionLanguage","Team:Visualizations","release_note:skip","backport:skip","v8.13.0"],"number":172738,"url":"https://github.com/elastic/kibana/pull/172738","mergeCommit":{"message":"[Lens] unify expression search context type (#172738)\n\n## Summary\r\n\r\nWhile working on #172710 I noticed\r\nhow loose our search context types were. This leeway seems like overkill\r\ngiven how we actually use the expressions framework.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"570937ff19c500d0d54b605b0602b6ffb2a6fb10"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/172738","number":172738,"mergeCommit":{"message":"[Lens] unify expression search context type (#172738)\n\n## Summary\r\n\r\nWhile working on #172710 I noticed\r\nhow loose our search context types were. This leeway seems like overkill\r\ngiven how we actually use the expressions framework.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"570937ff19c500d0d54b605b0602b6ffb2a6fb10"}}]}] BACKPORT--> Co-authored-by: Kibana Machine <[email protected]>
Summary
While working on #172710 I noticed how loose our search context types were. This leeway seems like overkill given how we actually use the expressions framework.