This is an automated email from the ASF dual-hosted git repository.
zhongjiajie pushed a commit to branch history-docs
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/history-docs by this push:
new 8e5fa8050 Correct parameter set syntax (#766)
8e5fa8050 is described below
commit 8e5fa8050b5e0ee0dee78224ede7e774517c2a44
Author: Jiajie Zhong <[email protected]>
AuthorDate: Wed Apr 6 12:33:06 2022 +0800
Correct parameter set syntax (#766)
---
.gitignore | 4 ++--
docs/2.0.0/docs/en/guide/parameter/context.md | 2 +-
docs/2.0.1/docs/en/guide/parameter/context.md | 2 +-
docs/2.0.2/docs/en/guide/parameter/context.md | 2 +-
docs/2.0.3/docs/en/guide/parameter/context.md | 2 +-
docs/2.0.5/docs/en/guide/parameter/context.md | 2 +-
6 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/.gitignore b/.gitignore
index 91986ee05..eb70661cb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -38,8 +38,8 @@ config.gypi
/index.html
/build/
/dist/
-/en-us/
-/zh-cn/
+en-us/
+zh-cn/
# Only for branch history-docs
asset/
diff --git a/docs/2.0.0/docs/en/guide/parameter/context.md
b/docs/2.0.0/docs/en/guide/parameter/context.md
index 90cb368d6..0a5f39f2f 100644
--- a/docs/2.0.0/docs/en/guide/parameter/context.md
+++ b/docs/2.0.0/docs/en/guide/parameter/context.md
@@ -54,7 +54,7 @@ There is only the value of "id". Although the user-defined
sql looks up the fiel
prop is user-specified. The direction is selected as OUT. The output is
defined as a parameter only when the direction is OUT. Data type can choose
different data structures as needed; the value part is not required to be
filled. The user needs to pass the parameter, and when defining the shell
script, the output format of ${setValue(key=value)} statement is required, key
is the prop of the corresponding parameter, and value is the value of the
parameter.
-For example, ` echo '${setValue (trans = Hello trans)}' `, set "trans" to
"Hello trans", and the variable trans can be used in downstream tasks:
+For example, `echo '${setValue(trans = Hello trans)}'`, set "trans" to "Hello
trans", and the variable trans can be used in downstream tasks:
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
diff --git a/docs/2.0.1/docs/en/guide/parameter/context.md
b/docs/2.0.1/docs/en/guide/parameter/context.md
index 90cb368d6..0a5f39f2f 100644
--- a/docs/2.0.1/docs/en/guide/parameter/context.md
+++ b/docs/2.0.1/docs/en/guide/parameter/context.md
@@ -54,7 +54,7 @@ There is only the value of "id". Although the user-defined
sql looks up the fiel
prop is user-specified. The direction is selected as OUT. The output is
defined as a parameter only when the direction is OUT. Data type can choose
different data structures as needed; the value part is not required to be
filled. The user needs to pass the parameter, and when defining the shell
script, the output format of ${setValue(key=value)} statement is required, key
is the prop of the corresponding parameter, and value is the value of the
parameter.
-For example, ` echo '${setValue (trans = Hello trans)}' `, set "trans" to
"Hello trans", and the variable trans can be used in downstream tasks:
+For example, `echo '${setValue(trans = Hello trans)}'`, set "trans" to "Hello
trans", and the variable trans can be used in downstream tasks:
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
diff --git a/docs/2.0.2/docs/en/guide/parameter/context.md
b/docs/2.0.2/docs/en/guide/parameter/context.md
index b37e97cec..062d5cd1b 100644
--- a/docs/2.0.2/docs/en/guide/parameter/context.md
+++ b/docs/2.0.2/docs/en/guide/parameter/context.md
@@ -54,7 +54,7 @@ There is only the value of "id". Although the user-defined
sql looks up the fiel
prop is user-specified. The direction is selected as OUT. The output is
defined as a parameter only when the direction is OUT. Data type can choose
different data structures as needed; the value part is not required to be
filled. The user needs to pass the parameter, and when defining the shell
script, the output format of ${setValue(key=value)} statement is required, key
is the prop of the corresponding parameter, and value is the value of the
parameter.
-For example, ` echo '${setValue (trans = Hello trans)}' `, set "trans" to
"Hello trans", and the variable trans can be used in downstream tasks:
+For example, `echo '${setValue(trans = Hello trans)}'`, set "trans" to "Hello
trans", and the variable trans can be used in downstream tasks:
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
diff --git a/docs/2.0.3/docs/en/guide/parameter/context.md
b/docs/2.0.3/docs/en/guide/parameter/context.md
index b04eebf17..1bd9c08d3 100644
--- a/docs/2.0.3/docs/en/guide/parameter/context.md
+++ b/docs/2.0.3/docs/en/guide/parameter/context.md
@@ -54,7 +54,7 @@ There is only the value of "id". Although the user-defined
sql looks up the fiel
prop is user-specified. The direction is selected as OUT. The output is
defined as a parameter only when the direction is OUT. Data type can choose
different data structures as needed; the value part is not required to be
filled. The user needs to pass the parameter, and when defining the shell
script, the output format of ${setValue(key=value)} statement is required, key
is the prop of the corresponding parameter, and value is the value of the
parameter.
-For example, ` echo '${setValue (trans = Hello trans)}' `, set "trans" to
"Hello trans", and the variable trans can be used in downstream tasks:
+For example, `echo '${setValue(trans = Hello trans)}'`, set "trans" to "Hello
trans", and the variable trans can be used in downstream tasks:
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
diff --git a/docs/2.0.5/docs/en/guide/parameter/context.md
b/docs/2.0.5/docs/en/guide/parameter/context.md
index b37e97cec..062d5cd1b 100644
--- a/docs/2.0.5/docs/en/guide/parameter/context.md
+++ b/docs/2.0.5/docs/en/guide/parameter/context.md
@@ -54,7 +54,7 @@ There is only the value of "id". Although the user-defined
sql looks up the fiel
prop is user-specified. The direction is selected as OUT. The output is
defined as a parameter only when the direction is OUT. Data type can choose
different data structures as needed; the value part is not required to be
filled. The user needs to pass the parameter, and when defining the shell
script, the output format of ${setValue(key=value)} statement is required, key
is the prop of the corresponding parameter, and value is the value of the
parameter.
-For example, ` echo '${setValue (trans = Hello trans)}' `, set "trans" to
"Hello trans", and the variable trans can be used in downstream tasks:
+For example, `echo '${setValue(trans = Hello trans)}'`, set "trans" to "Hello
trans", and the variable trans can be used in downstream tasks:
<img src="/img/globalParam/trans-shell.png" alt="trans-shell"
style="zoom:50%;" />
