[CONTEDIT-124] Move type-mappings and component definitions from article-editor to content-editor Created: 04/Jul/17  Updated: 24/Jul/17  Resolved: 21/Jul/17

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: 1.0.5
Fix Version/s: 1.0.6

Type: Task Priority: Major
Reporter: Ilgun Ilgun Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by CONTEDIT-130 Adjust and move generic components to... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Stories App Demo
Sprint: Basel 104, Basel 105
Story Points: 2

 Description   

In the workshop we had realised that type-mapping's are missing if you want to have your own content-editor instance. Article-editor already contains those and those should moved to content-editor ideally.

Additionally, 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.

After properly defining those components in content-editor, the corresponding entries in article-editor and stories-app can be dropped.



 Comments   
Comment by Philip Mundt [ 19/Jul/17 ]

We found a nice solution which allows us to specify components only once.

Generated at Mon Feb 12 00:17:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.