[Lens] Lens embeddable hardcodes the supportedTriggers #61605
Labels
Feature:Lens
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
technical debt
Improvement of the software architecture and operational architecture
We currently have a hardcoded list in the
supportedTriggers
method in the Lens embeddable. This works fine right now, because other plugins currently can't register any own visualizations. I consider this to be a tech-debt, that we hardcode that list, since it prevents us from other plugins and solutions providing own visualizations into Lens. We should instead have the visualiation implementation let decide about what triggers it supports.Similar issue for visualize embeddable: #61601
The text was updated successfully, but these errors were encountered: