mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
11b750b10a
## Summary  At the moment, our package generator creates all packages with the type `shared-common`. This means that we cannot enforce boundaries between server-side-only code and the browser, and vice-versa. - [x] I started fixing `packages/core/*` - [x] It took me to fixing `src/core/` type to be identified by the `plugin` pattern (`public` and `server` directories) vs. a package (either common, or single-scoped) - [x] Unsurprisingly, this extended to packages importing core packages hitting the boundaries eslint rules. And other packages importing the latter. - [x] Also a bunch of `common` logic that shouldn't be so _common_ 🙃 ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| agent.ts | ||
| artifact_manager.ts | ||
| cli_config.ts | ||
| config.ts | ||
| fleet_server.ts | ||
| ftr_provider_context.d.ts | ||
| resource_manager.ts | ||
| runner.ts | ||
| services.ts | ||
| visual_config.ts | ||