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 ApplicationService's legacyMode #74911

Closed
joshdover opened this issue Aug 12, 2020 · 1 comment · Fixed by #75987
Closed

Remove ApplicationService's legacyMode #74911

joshdover opened this issue Aug 12, 2020 · 1 comment · Fixed by #75987
Assignees
Labels
chore Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

Once #73154 merges, it will finally be impossible to run legacy UI plugins. We can then remove the "legacy mode" from the core application service and simplify quite a bit of our routing layer to only support KP plugins.

@joshdover joshdover added chore Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Aug 12, 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
chore Feature:New Platform 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