-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Renderers for all visualizations #46801
Labels
Feature:Visualizations
Generic visualization features (in case no more specific feature label is available)
loe:x-large
Extra Large Level of Effort
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Comments
streamich
added
Feature:Visualizations
Generic visualization features (in case no more specific feature label is available)
Team:AppArch
labels
Sep 27, 2019
Pinging @elastic/kibana-app-arch |
timroes
added
the
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
label
Sep 15, 2020
This was referenced Sep 23, 2020
4 tasks
4 tasks
Closing this in favor of #78578 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Visualizations
Generic visualization features (in case no more specific feature label is available)
loe:x-large
Extra Large Level of Effort
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
All visualization renderers should be migrated from current infrastructure to expression renderers. This will make them reusable outside of visualize (currently that is lens and canvas) and allow us to deprecate visualization renderers infrastructure thus making visualization infrastructure simpler.
vis types would still continue to exist, the only difference being that instead of providing a visualization renderer in the vis definition expression renderer is provided instead. Vis type also needs to expose a function
toAST
that allows us to convert vis.params into expression ast.list of visualizations to convert:
visualizations
plugin infrastructure, including removal ofbuildPipeline
in exchange for creating an expression ast, remove react & default renderer (see also Visualization infrastructure cleanup #78578)Parent issue: #44121
The text was updated successfully, but these errors were encountered: