Migrating away from ui/public #26505
Labels
chore
Feature:NP Migration
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
the functionality in
ui/public
is exposed to all plugins. It has things like query bar logic, embeddable stuff, filters, courier, saved objects, some ui components, etc. Having this open directory is a problem for us though:As we strive for a system that is more supportive of our plugin developers, we would like to fix this and replace it with code that has clear boundaries and exposes only very specific functionality. An API, that if changed, we know to issue BWC (backward compatibility) breaking change warnings, and an API that is also well documented.
This means migrating away from
ui/public
. We came up with a few locations the different types of folders belong in:src/core
- New platform for services central to the new platform; save to object etc. basicspackages
: stateless libraries, utilities...src/plugins
: visualizer, dashboard, index strings, canvas,...src/legacy/ui/public
: Stuff that will be going away and isn't worth migrating anywhere.We got together in Dublin and came up with this separation. It could go for another review, but this gives us a place to start.
src/core
packages
[src/plugin]
draggable
)src/legacy/ui/public
The text was updated successfully, but these errors were encountered: