You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ro...@apache.org on 2016/02/18 11:54:15 UTC
svn commit: r1731045 -
/sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext
Author: rombert
Date: Thu Feb 18 10:54:15 2016
New Revision: 1731045
URL: http://svn.apache.org/viewvc?rev=1731045&view=rev
Log:
SLING-5523 - filter pipe should be able to filter out resources that *have* a configured child
Submitted-By: Nicolas Peltier
Modified:
sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext
Modified: sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext?rev=1731045&r1=1731044&r2=1731045&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/sling-pipes.mdtext Thu Feb 18 10:54:15 2016
@@ -102,6 +102,7 @@ outputs the input resource if its matche
- `conf` node tree that will be tested against the current input of the pipe, each `/conf/sub@prop=value` will triggers a test
on `./sub@prop` property of the current input, testing if its value matches `value` regex. If the special `slingPipesFilter_noChildren=${true}`
property is there with the value instantiated as a true boolean, then filter will pass if corresponding node has no children.
+- `slingPipesFilter_not='true'` inverts the expected result of the filter
### containers
#### Container Pipe