Add a legacy compatibility layer for ApplicationService #46481
Labels
Feature:New Platform
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Legacy plugins cannot currently use the
core.application.register
API. If they attempt to call it, an exception is throw immediately.To ease migrations, we should be able to add a legacy version of this API that uses the Legacy
chrome.setRootController
API under the hood in order to provide a NP-compatible API to Legacy plugins.The text was updated successfully, but these errors were encountered: