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

Create tool to identify plugin import dependencies to support TS project references migration #79343

Closed
joshdover opened this issue Oct 2, 2020 · 1 comment · Fixed by #80463
Assignees
Labels
Feature:Development Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

joshdover commented Oct 2, 2020

Related to #46773

From this comment: #78586 (comment)

We need to create a tool that allows us to see the import dependency tree of plugins so that we can correctly identify the order that we need to migrate plugins to projects in. This is necessary because all of a plugin's dependencies must be converted to a TS project before itself can be.

@joshdover joshdover added Feature:Development Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Oct 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Development Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants