[Lens] make visualization_ui_components plugin a static package #161140
Labels
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
technical debt
Improvement of the software architecture and operational architecture
Describe the feature:
As we move more of our code to a stateless context, we reap benefits of increased simplicity and verifiability, leading to higher quality and stability.
The visualization_ui_components plugin was created to make Lens UI components available outside of Lens as the need arises (e.g. #158774).
It was originally planned as a static package, but I made it a plugin because of a dependency on a Unified Search component which, being in a
public
context, could not be imported from a static package context.However, most of the current plugin could be pulled out into a static package following the pattern used in #158008 where we put what we can in static packages that are then injected with Kibana dependencies via a slim plugin wrapper.
The text was updated successfully, but these errors were encountered: