-
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
[PieVis] Chart expressions pie. #121612
[PieVis] Chart expressions pie. #121612
Conversation
# Conflicts: # src/plugins/chart_expressions/expression_pie/common/expression_functions/pie_vis_function.test.ts
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
@elasticmachine merge upstream |
@elastic/kibana-vis-editors, folks, could you, please, review the current PR?) Thanks a lot ) |
@elasticmachine merge upstream |
@elastic/kibana-vis-editors, folks, could you, please, review the current PR?) Thanks a lot ) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
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.
This works great. It hasn't changed the api at all, we just moving files around. I only have two comments to remove things that are not needed.
@@ -45,24 +42,10 @@ export interface VisTypePieDependencies { | |||
export class VisTypePiePlugin { | |||
setup( | |||
core: CoreSetup<VisTypePiePluginStartDependencies>, | |||
{ expressions, visualizations, charts, usageCollection }: VisTypePieSetupDependencies |
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.
We can also remove the expressions from the VisTypePieSetupDependencies
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.
My bad, sorry) Done.
export class ExpressionPiePlugin { | ||
public setup( | ||
core: CoreSetup<VisTypePiePluginStartDependencies>, | ||
{ expressions, visualizations, charts, usageCollection }: SetupDeps |
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.
The visualizations and usageCollection are not used here, let's remove them. We can also remove the usageCollection from the kibana.json required plugins
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.
Sure, thanks. Done)
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 applying my comments! Code changes LGTM, I tested it on Chrome and works fine. Please feel free to merge in case of green CI
@stratoula, thanks a lot) |
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
async chunk count
ESLint disabled line counts
References to deprecated APIs
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @Kunzetsov |
Summary
Completes a part of #107500.
At this PR
pieVis
function
andrenderer
have been moved tochart_expressions/expression_pie
.