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

[new-platform] migrate chrome UI to the new platform #27086

Closed
spalger opened this issue Dec 12, 2018 · 1 comment · Fixed by #39300
Closed

[new-platform] migrate chrome UI to the new platform #27086

spalger opened this issue Dec 12, 2018 · 1 comment · Fixed by #39300
Assignees
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@spalger
Copy link
Contributor

spalger commented Dec 12, 2018

This was originally a part of #19992, but we broke it out in order to ship the k7 design before doing the work to migrate all extension points into the chrome to the new platform.

Now that all services that the Header component depends on are available in the new platform, move the rendering of this UI to the new platform. This is a per-requisite to being able to have new platform applications.

@spalger spalger added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Dec 12, 2018
@spalger spalger self-assigned this Dec 12, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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