You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
user would like to modify properties of a /my/path/to/some/node
some properties should be set as defined, i.e. property1 = value1
the remaining ones should be merged with existing value, ie. property2 = aaa, user defined property2 as bbb and expected value is aaabbb
at the same time it'd be great to completely ignore existing values in cq_jcr's properties, so it gets automatically read and concatenated with value defined by user
append property exists today, but it is considered global and its role is to either ensure that only properties defined in cq_jcr should be set or we'd like to append new properties to existing state (at the same time we don't really care how many properties exist and what values are assigned to them).
The very first solution that came to my mind is brand new cq_jcr property that defines merge strategy for each property, for example:
I just encountered the following case:
/my/path/to/some/node
property1 = value1
property2 = aaa
, user definedproperty2
asbbb
and expected value isaaabbb
cq_jcr
's properties, so it gets automatically read and concatenated with value defined by userappend
property exists today, but it is considered global and its role is to either ensure that only properties defined incq_jcr
should be set or we'd like to append new properties to existing state (at the same time we don't really care how many properties exist and what values are assigned to them).The very first solution that came to my mind is brand new
cq_jcr
property that defines merge strategy for each property, for example:At the time of writing I'm not sure though if that's the right way to go. It definitely requires some design session.
The text was updated successfully, but these errors were encountered: