[
https://issues.apache.org/jira/browse/SLING-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064644#comment-17064644
]
Bertrand Delacretaz commented on SLING-9171:
--------------------------------------------
I agree with the need for these modes but I don't find "merge" and "update" to
have an intuitive meaning.
Also, setting the options at the block level means having to repeat a block
with the same list of paths if some properties need one mode and others need
another, which can lead to errors with inconsistent lists of paths between the
blocks or duplicated properties.
I would rather suggest this alternate syntax where "default" means "don't
change if already set". We might use "setdef" instead of "default" if
preferred, to make sure people look the docs up to understand exactly what
"setdef" means.
{code}
set properties on /pathA, /path/B
set sling:ResourceType to /x/y/z
set cq:allowedTemplates to /d/e/f/, m/n/
default someInteger{Integer} to 42
default someFlag{Boolean} to true
default title to "This is the default title"
end
{code}
> Support for settings properties on paths created via repoinit create path
> -------------------------------------------------------------------------
>
> Key: SLING-9171
> URL: https://issues.apache.org/jira/browse/SLING-9171
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: Nitin Gupta
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Apart from jcr:primaryType and mixin, there is a requirement to add custom
> properties to the nodes valuemap via repoinit. This is a gap currently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
