Collections of Collections break the editor


When you start exploring the possibilities of multi collection setups you start running into inconsistencies and errors.

e.g: say we have a footer configuration which has the option to create columns which in turn contain a bunch of links (pushing that one step further you could say that MenuLinkConfig contains another property for another hierarchical menu which again contains links)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 @Configuration( label = "Footer Configuration", description = "Add footer navigation, footer branding and social configuration" ) // I've left this here intentionally so when we fix the editor we can just use this instead of the fragmented column approach public @interface FooterConfig { @Property( label = "Navigational menu's", description = "Define multiple menu's which usually will be rendered in order of definition. Please note that configuration and rendering are not necessarily a 1-on-1 match", order = 200 ) MenuConfig[] menu(); } public @interface MenuConfig { @Property(label = "Links", description = "Configure a list of links") MenuLinkConfig[] links(); } public @interface MenuLinkConfig { @Property( label = "Link Text", description = "Configure a link text, when this is available, this will receive preference over nav and page title [Optional]", order = 200 ) String linkText(); @Property( label = "Link", description = "Configure the link to an internal page via the path browser or enter an absolute URL [Optional]", property = { "widgetType=pathbrowser", "pathbrowserRootPath=/content" }, order = 300 ) String link(); }


  • after adding the footer config for the first time it seems at some point of adding configs you need to reload the entire editor app to be able to add the next item - it sometimes seems to forget what exactly it's editing and usually misses the collectionItemName in between the path. e.g. /menu/links instead of /menu/menu1/links.

Note: strangely enough a reload of the entire editor seems to momentarily fix the issue - this seems to suggest it's somewhere in the angular app which loses its footing at some point







Bart Wulteputte




Affects versions

Context-Aware Configuration Editor 1.3.2