SbloodyS commented on code in PR #9671:
URL: https://github.com/apache/dolphinscheduler/pull/9671#discussion_r856126805
##########
docs/docs/en/guide/parameter/context.md:
##########
@@ -55,7 +55,15 @@ There is only the "id" value. Although the user-defined SQL
query both "id" and
### SHELL
`prop` is user-specified and the direction is `OUT`. The output is defined as
an export parameter only when the direction is `OUT`. Choose data structures
for data type according to the scenario, and leave the value part blank.
-The user needs to pass the parameter when creating the shell script, the
output statement format is `${setValue(key=value)}`, the key is the `prop` of
the corresponding parameter, and value is the value of the parameter.
+
+The user needs to pass the parameter when creating the shell script, the
output statement format is `${setValue(key=value)}` or
`#{setValue(key=value)}`, the key is the `prop` of the corresponding parameter,
and value is the value of the parameter.
Review Comment:
```suggestion
If the user needs to pass the parameter when creating the shell script. The
output statement format is `${setValue(key=value)}` or
`#{setValue(key=value)}`. the key is the `prop` of the corresponding parameter.
And value is the value of the parameter.
```
##########
docs/docs/zh/guide/parameter/context.md:
##########
@@ -57,13 +57,19 @@ prop 为用户指定；方向选择为 OUT，只有当方向为 OUT 时才会被
prop 为用户指定；方向选择为 OUT，只有当方向为 OUT 时才会被定义为变量输出；数据类型可以根据需要选择不同数据结构；value 部分不需要填写。
-用户需要传递参数，在定义 shell 脚本时，需要输出格式为 ${setValue(key=value)} 的语句，key 为对应参数的
prop，value 为该参数的值。
+用户需要传递参数，在定义 shell 脚本时，需要输出格式为 `${setValue(key=value)}` 或者
`#{setValue(key=value)}` 的语句，key 为对应参数的 prop，value 为该参数的值。
Review Comment:
```suggestion
如果用户需要传递参数，在定义 shell 脚本时，需要输出格式为 `${setValue(key=value)}` 或者
`#{setValue(key=value)}` 的语句，key 为对应参数的 prop，value 为该参数的值。
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
