-
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
[Canvas] Expression progress #104457
[Canvas] Expression progress #104457
Conversation
05f87a2
to
9d7f2d6
Compare
Pinging @elastic/kibana-presentation (Team:Presentation) |
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.
Everything looks good. Need to figure out those class names that start with "canvas"
@@ -1,8 +1,9 @@ | |||
/* | |||
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one | |||
* or more contributor license agreements. Licensed under the Elastic License | |||
* 2.0; you may not use this file except in compliance with the Elastic License | |||
* 2.0. | |||
* 2.0 and the Server Side Public License, v 1; you may not use this file except |
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 caused the need to move this file to pres_util?
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.
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.
I'd like to try to keep presentation_util as only things that are really presentation related. Can we just inline the id generation on the SVG?
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.
Updated PR based on your nit.
const BarProgress = shapeData.shapeType ? getShapeContentElement(shapeData.shapeType) : null; | ||
|
||
const shapeContentAttributes = { | ||
className: 'canvasProgress__background', |
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 need to get rid of all these canvas_
prefixed class names since this is not strictly canvas anymore. Are they even used for anything at this point? Can you double check on that?
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.
Removed this canvas*
classes. According to the code, it is not necessary, but, possibly, some tests were using it. After passing the CI we'll see)))
# Conflicts: # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
@elasticmachine merge upstream |
@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.
Looks good to go 👍
💔 Backport failed
To backport manually run: |
* Added `expression_progress` plugin. Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # packages/kbn-optimizer/limits.yml
* [Canvas] Expression progress (#104457) * Added `expression_progress` plugin. Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # packages/kbn-optimizer/limits.yml * Update limits.yml
* Added `expression_progress` plugin. Co-authored-by: Kibana Machine <[email protected]>
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsAPI count
API count missing comments
async chunk count
References to deprecated APIs
History
To update your PR or re-run it, just comment with: cc @Kunzetsov |
Completes a part of #101377.
At this PR progress expression is extracted from the canvas plugin and set up as a separate plugin.
List of required changes to be done:
progress
expression from canvas to a separate plugin.ts
andReact
.Storybook
for theprogress
expression renderer.canvas
pluginTesting Notes
This moves the progress expression function to a standalone plugin and refactors the code. To test, just test that the progress expression in canvas continues to work as expected.