[
https://issues.apache.org/jira/browse/SLING-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418984#comment-17418984
]
Konrad Windszus commented on SLING-10645:
-----------------------------------------
IMHO the whole logic is already quite complicated. Having more options just for
multivalue properties is a bit tricky to do in a backwards compatible way. The
proposed solution from
https://issues.apache.org/jira/browse/SLING-10645?focusedCommentId=17410633&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17410633
is not enough, as it disregards the fact, that multi-values have an order, so
there must be way to express where to insert it.
I don't see a simple solution which allows to
- remove some values (by index, as there might be several times the same value
in the property)
- add some value (by index to specify the order)
with a simple property as for the latter you would have to give both: index and
new value.
[~Henry Kuijpers] Do you have a (simple) proposal which correctly considers the
order?
> 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)
