This is an automated email from the ASF dual-hosted git repository.
npeltier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 7f53c9c [pipes] add documentation for prepared release
7f53c9c is described below
commit 7f53c9c95d7a40d63cef4e37f6955dec9ec6f2ca
Author: Nicolas Peltier <[email protected]>
AuthorDate: Tue Feb 12 11:46:55 2019 +0100
[pipes] add documentation for prepared release
SLING-8126, SLING-8130
---
.../jbake/content/documentation/bundles/sling-pipes/bindings.md | 9 +++++++--
.../jbake/content/documentation/bundles/sling-pipes/writers.md | 4 +++-
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git
a/src/main/jbake/content/documentation/bundles/sling-pipes/bindings.md
b/src/main/jbake/content/documentation/bundles/sling-pipes/bindings.md
index 053d7a4..8e1b1d0 100644
--- a/src/main/jbake/content/documentation/bundles/sling-pipes/bindings.md
+++ b/src/main/jbake/content/documentation/bundles/sling-pipes/bindings.md
@@ -59,8 +59,11 @@ will loop twice on the pipe `example`, making available each
time for the follow
## additional bindings
-additional bindings is a [node you add to your pipe
definition](/documentation/bundles/sling-pipes/execution-monitoring.html#jcr-persistence-of-a-pipe.html),
that
-sets bindings for the whole pipe execution.
+`additionalBindings` is a [node you add to any pipe
definition](/documentation/bundles/sling-pipes/execution-monitoring.html#jcr-persistence-of-a-pipe.html),
that
+sets its properties as bindings for this pipe's context execution.
+you can also add `additionalBindings/providers` children, that should be
read-only pipes that will get executed before this pipe
+execution, to provide dynamic bindings.
+
You can also add some through [pipe builder
api](/documentation/bundles/sling-pipes/execution-monitoring.html#pipe-builder-api)
with a map of bindings
@@ -73,6 +76,8 @@ or with a set of key / value pairs
[http
api](/documentation/bundles/sling-pipes/execution-monitoring.html#http-api) for
this is a binding parameter
-F bindings='{"env":"prod"}'
+
+In case a pipe needs a more dynamic binding, you can use another pipe as
binding provider,
## additional scripts
diff --git
a/src/main/jbake/content/documentation/bundles/sling-pipes/writers.md
b/src/main/jbake/content/documentation/bundles/sling-pipes/writers.md
index 8f56411..f8d68f1 100644
--- a/src/main/jbake/content/documentation/bundles/sling-pipes/writers.md
+++ b/src/main/jbake/content/documentation/bundles/sling-pipes/writers.md
@@ -22,8 +22,10 @@ e.g.
will write `@foo1=bar1` and `@foo2=bar2` in `/content/foo`. For more
complicated cases where you need a structure to be written,
just use a JCR / Resource explorer to edit the persistence of the pipe, and
create the given structured under conf.
+Note that you can use expressions in that node tree, and specifically, for a
node name, parent of a tree you want to
+be conditionally written, use `$if${...}nodename` syntax, that will basically
only create such tree if the expression is true.
-Note that using `expr` you need configuration node _not_ to be here, and
{{write}} shortcut creates one systematically.
+Note that using `expr` you need configuration node _not_ to be here, and
`write` shortcut creates one systematically.
So if you want to use pipe builder and that, you'd need something like
.echo('/content/destination')
