Skip to content
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

Remove circular dependency between discover & visualizations plugins #80511

Closed
mshustov opened this issue Oct 14, 2020 · 2 comments · Fixed by #82248
Closed

Remove circular dependency between discover & visualizations plugins #80511

mshustov opened this issue Oct 14, 2020 · 2 comments · Fixed by #82248
Labels
Feature:Discover Discover Application Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@mshustov
Copy link
Contributor

discover plugin lists visualizations in requiredPlugins, while visualizations declares discover plugin as requiredBundles.
We need to remove circular dependency to unblock plugin migration to TS project refs #80508 and migration to the new build chain #69706

@mshustov mshustov added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Oct 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@timroes
Copy link
Contributor

timroes commented Oct 20, 2020

The way we should resolve that is by making Discover not require the visualizations plugin anymore. It's solely using it for the purpose of creating a vis for the histogram bar chart. Actually we never need that Vis object in discover and instead we could and should just request the data using esaggs directly and input that into the custom renderer we're using in discover. Solving this issue, will automatically also solve #69134 which we anyway planned to do soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Discover Discover Application Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants