Migrate chrome to EUI #19992
Assignees
Labels
Feature:New Platform
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Comments
epixa
added
chore
Team:Core
|
@spalger I assigned this to you since you need to overhaul the chrome for new platform app bundles anyway, so this work likely just falls out naturally from that. |
4 tasks
spalger
pushed a commit
that referenced
this issue
Jul 19, 2018
In order to make the awesome new kfetch api easier to consume in purely TypeScript projects, and since it's a pretty small module with very few dependencies, I converted it to TypeScript. Along with kfetch I also started a type definition file for `ui/chrome` that we can extend as we go, but will likely be unnecessary after #19992
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
Jul 19, 2018
In order to make the awesome new kfetch api easier to consume in purely TypeScript projects, and since it's a pretty small module with very few dependencies, I converted it to TypeScript. Along with kfetch I also started a type definition file for `ui/chrome` that we can extend as we go, but will likely be unnecessary after elastic#19992
spalger
pushed a commit
that referenced
this issue
Jul 19, 2018
In order to make the awesome new kfetch api easier to consume in purely TypeScript projects, and since it's a pretty small module with very few dependencies, I converted it to TypeScript. Along with kfetch I also started a type definition file for `ui/chrome` that we can extend as we go, but will likely be unnecessary after #19992
This was referenced Sep 15, 2018
joshdover
changed the title
|
We decided to implement the K7 EUI header entirely in the old platform, mainly because the plugin API for new platform has not been implemented yet. Plugins interact with the header by placing custom UI as "nav controls" (eg. security's logout UI) and by updating breadcrumbs in the new header. To unblock K7 for 7.0, we put the new EUI header in the old platform, though still implemented as a React component. |
|
Extracted the migration to the new platform to #27086 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In preparation for the K7 design and to support the new platform, we need to replace the chrome UI with EUI components.
We'll take care of this when we move the
ui/chromeUI out of the legacy platform and into the new platform, after #20696 is complete.Should support:
The text was updated successfully, but these errors were encountered: