[
https://issues.apache.org/jira/browse/SLING-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410633#comment-17410633
]
Henry Kuijpers commented on SLING-10645:
----------------------------------------
Anyone with a strong opinion on how to approach this ticket?
Otherwise, I'd propose the following:
Existing properties:
* sling:hideProperties=[x,y,z]
* sling:hideChildren=[x,y,z]
* sling:orderBefore[x,y,z]
* sling:hideResource=true/false
Extra properties:
* sling:hidePropertyValues=[x=not-desired,x=also-not-desired,y=not-desired]
*
sling:addPropertyValues=[x=desired-but-not-existent-in-parent,y=desired-in-y-property]
The extra properties would be there to be able to patch multivalued properties,
instead of hiding/overriding the entire set of values from the parent.
WDYT [~bdelacretaz] [~kwin] [~cziegeler]?
> Update Sling Resource Merger with handling for multi-valued properties
> ----------------------------------------------------------------------
>
> Key: SLING-10645
> URL: https://issues.apache.org/jira/browse/SLING-10645
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Merger 1.4.0
> Reporter: Henry Kuijpers
> Priority: Major
>
> Sling Resource Merger is able to handle properties, not individual property
> values.
> When setting up this node structure (with AEM's extraClientlibs property in
> TouchUI dialogs):
> + /libs/wcm/basicpage/cq:dialog@extraClientlibs=["a", "b", "c"]
> + /apps/website/components/page@sling:resourceSuperType="wcm/basicpage"
> + /apps/website/components/page/cq:dialog@extraClientlibs=["d", "e"]
> We want to make sure that the extraClientlibs property that is being read in
> website/components/page/cq:dialog will return ["a", "b", "c", "d", "e"].
> Currently, it will just return ["d", "e"], since the extraClientlibs-property
> is *overwritten*.
> It would be nice to add additional logic to allow more control over the
> inheritance of the values that are tied to a parent's
> extraClientlibs-property.
> Maybe we can come up with some additional properties that can function as
> instructions to the Resource Merger (next to the ones we already have), so
> that there can be more fine-grained control over the inheritance/removal of
> property values in multi-valued scenarios.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
