[
https://issues.apache.org/jira/browse/SLING-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226022#comment-14226022
]
ASF GitHub Bot commented on SLING-4011:
---------------------------------------
GitHub user kwin opened a pull request:
https://github.com/apache/sling/pull/48
SLING-4011 allow regular expressions for resource names and property names
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kwin/sling SLING-4011-validatorwildcardsupport
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/48.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #48
----
commit b10a838264068c4b375d9b08a822ddd6ff908458
Author: Konrad Windszus <[email protected]>
Date: 2014-11-25T17:06:44Z
SLING-4011 allow wildcard matching for childresources
commit 0b9d48afa424723aa9d34866baa566dfdebe627a
Author: Konrad Windszus <[email protected]>
Date: 2014-11-26T10:54:06Z
SLING-4011, allow name regex for properties, refactor tests
----
> Allow ValidationModel nodes in the JCR contain wildcards below children and
> properties
> ---------------------------------------------------------------------------------------
>
> Key: SLING-4011
> URL: https://issues.apache.org/jira/browse/SLING-4011
> Project: Sling
> Issue Type: Improvement
> Components: Validation
> Reporter: Konrad Windszus
> Labels: validator
> Fix For: Validation 1.0.0
>
>
> According to
> https://github.com/apache/sling/blob/trunk/contrib/validation/README.md the
> nodes in the JCR specifying a validation model must always give an explicit
> property name or child node name. This is sometimes not possible if the
> subnodes/properties are generated automatically. Therefore it would be great
> if the elements directly below {{children}} and {{properties}} would allow
> wildcards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
