-
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] lens_multitable
removal.
#131699
[Lens] lens_multitable
removal.
#131699
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.
Looks mostly good to me, just one thing that looks a little suspicious
@@ -48,6 +48,8 @@ export default function ({ getService, getPageObjects }: FtrProviderContext) { | |||
}); | |||
|
|||
it('should reflect edits for gauge', async () => { | |||
await PageObjects.lens.switchToVisualization('horizontalBullet', 'gauge'); |
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.
What are these changes about? It should work just fine without this change, right?
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.
If you'll run the test via grep
by picking the current test case, it will fail. According to the FIRST principle of testing, a test should set up its own data and should not depend on any external factors to run its test. So, that is not really the right behavior, if the test is failing if ran separately from the previous test case. @flash1293, WDYT?
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 LGTM
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, thanks for the explanation.
I'm not opposed to "drive by" improvements like this per se, but please call them out in the description, this makes it much easier to follow the changes.
@flash1293, @VladLasitsa, thanks for the approval 🎉 . Sure, will do that in the future. |
# Conflicts: # x-pack/plugins/lens/public/datatable_visualization/components/table_actions.ts # x-pack/plugins/lens/public/xy_visualization/to_expression.ts
@elastic/kibana-gis, could you, please, review this PR. Thanks 😃 |
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.
kibana-gis changes LGTM
code review, tested in chrome
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @Kunzetsov |
Summary
lens_multitable
expression andshouldBuildDatasourceExpressionManually
function from theVisualization
interface, as was mentioned at the comment.gauge
at the functional test to make it isolated and repeatable.