-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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] create base new platform bundle #18875
Labels
Feature:New Platform
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Comments
epixa
added
the
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
label
May 9, 2018
Splitting up into
|
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
Part of #16253
Until we get #10908 we want a solution for working and shipping new-platform stuff in the UI. To get started we will create a new bundle in the optimizer dedicated for the new platform. This bundle will be loaded any time a
uiExports.app
is not found for an application, allowing it to find the application in the newPlatform bundle or render a 404 page.With this mechanism the server doesn't need to know about any plugin-provided apps, "legacy" applications can continue to exist in their current form, and we can start figuring out more new-platform stuff.
newPlatform
bundle in the optimizerThe text was updated successfully, but these errors were encountered: