Mailing-List: contact dev-help@sling.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sling.apache.org
Date: Mon, 21 Aug 2017 08:29:00 +0000 (UTC)
From: "Timothee Maret (JIRA)" <jira@apache.org>
To: dev@sling.apache.org
Message-ID: <JIRA.13096371.1503304048000.77208.1503304140881@Atlassian.JIRA>
In-Reply-To: <JIRA.13096371.1503304048000@Atlassian.JIRA>
References: <JIRA.13096371.1503304048000@Atlassian.JIRA> <JIRA.13096371.1503304048847@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (SLING-7066) Support mixins in repoinit "create
 path" statements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 21 Aug 2017 08:29:08 -0000


     [ https://issues.apache.org/jira/browse/SLING-7066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothee Maret reassigned SLING-7066:
-------------------------------------

    Assignee: Timothee Maret

> Support mixins in repoinit "create path" statements
> ---------------------------------------------------
>
>                 Key: SLING-7066
>                 URL: https://issues.apache.org/jira/browse/SLING-7066
>             Project: Sling
>          Issue Type: New Feature
>          Components: Repoinit
>            Reporter: Bertrand Delacretaz
>            Assignee: Timothee Maret
>            Priority: Minor
>
> The repoinit "create path" statement currently supports nodetypes but no mixins, we should add support for them.
> The current create path syntax is like
> {code}
> create path (sling:Folder) /var/discovery(nt:unstructured)/somefolder
> create path /one/two/three
> create path /three/four(nt:folk)/five(nt:jazz)/six
> {code}
> Where the first bracketed statement, before the path, is the default nodetype for all subpaths, and each subpath can have a specific nodetype.
> To add mixin support I suggest the syntax of these examples for these bracketed statements:
> {code}
> (sling:Folder mixin mix:A, mix:B)
> (nt:unstructured mixin mix:C)
> (mixin mix:A)
> (mixin mix:A, mix:B)
> {code}
> The last two forms without a nodeteype meaning "set mixins only but keep the default nodetype", which in this example
> {code}
> create path (sling:Folder) /var/foo(mixin mix:B)
> {code}
> means /var/foo is of type sling:Folder with mixin mix:B
> whereas in this example
> {code}
> create /var/bar(mixin mix:C)
> {code}
> /var/bar uses the default type defined by /var's type, with mix:C added.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)