Details
-
Improvement
-
Resolution: Duplicate
-
Neutral
-
None
-
None
-
None
Description
Currently, several components need to be explicitly declared in (sub-)app scope for modules implementing a content editor:
- info.magnolia.editor.content.blockpicker.BlockTypePicker
- info.magnolia.editor.content.blockpicker.BlockPickerHelper
- info.magnolia.editor.content.blockpicker.BlockRegistryContentConnector
- info.magnolia.editor.content.ContentDefinition
This is a unfortunate because those types are quite generic and most of the times, standard implementations from content-editor will be used, leading to unnecessary boilerplate configuration.
However, we cannot directly move those definitions to content-editor yet because they would need to live in main scope, but have dependencies to (sub-)app-specific components. As a workaround, we could refactor those classes to lazy-load (sub-)app-related objects using factories/providers.
After properly defining those components in content-editor, the corresponding entries in article-editor and stories-app can be dropped.
Checklists
Attachments
Issue Links
- duplicates
-
CONTEDIT-124 Move type-mappings and component definitions from article-editor to content-editor
-
- Closed
-