Kibana app migration: Extension points

[kertal]

List of registries used in src/legacy/core_plugins/kibana

• ui/registry/feature_catalogue Migrate ui/registry/feature_catalogue to New Platform #46738
• ui/registry/field_formats Use NP registry instead of ui/registry/field_formats  #48108
• ui/registry/field_format_editors
• ui/registry/doc_views should be migrated to Discover, just used there
• ui/registry/vis_editor_types
• ui/registry/dev_tools
• ui/share (ShareContextMenuExtensionsRegistryProvider) Migrate share registry #50137
• ui/saved_objects/saved_object_registry (SavedObjectRegistryProvider)
• src/legacy/core_plugins/kibana/public/dashboard/dashboard_config.js do not migrate

[flash1293]

I chatted with @timroes about this, here are some notes:

• To not block migration, we should move the dev_tools registry and share registry to the NP as a separate plugin. For dev tools, the registry can be the first part of the NP plugin with the app itself following with the cutover. For share, the registry should stay in a separate plugin because the registry is used from multiple plugins.
• doc_views can stay in the legacy plugin and support angular as long as possible to not break 3rd party plugins without need
• field formatters will be migrated by AppArch ( @ppisljar is this also the case for vis_editor_types?)

fyi @kertal

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[flash1293]

field_format_editors and vis_editor_types were taken care of by the app arch team, closing this.