Skip to content

[Improvement-18045][Doc]Improvement Parameter passing behavior doc#18046

Merged
SbloodyS merged 7 commits intoapache:devfrom
njnu-seafish:Improvement-18045
Mar 16, 2026
Merged

[Improvement-18045][Doc]Improvement Parameter passing behavior doc#18046
SbloodyS merged 7 commits intoapache:devfrom
njnu-seafish:Improvement-18045

Conversation

@njnu-seafish
Copy link
Copy Markdown
Contributor

Was this PR generated or assisted by AI?

NO

Purpose of the pull request

close #18045

Brief change log

Improvement Parameter passing behavior doc

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(or)

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

> In older version before 3.2.2, downstream node B could obtain the out type output X of upstream node A without configuring an IN type local variable X.
> In the new version after 3.3.0, the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.
> In legacy versions (3.2.2 and earlier), downstream node B could obtain the out type output X of upstream node A without configuring an IN type local variable X.
> In new versions (3.3.0 and later), the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.(Note: This restriction does not apply to Switch tasks, as they lack an interface for configuring custom parameters.)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> In new versions (3.3.0 and later), the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.(Note: This restriction does not apply to Switch tasks, as they lack an interface for configuring custom parameters.)
> In new versions (3.3.0 and later), the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.

We don't need this since this should be placed in the switch task type.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need this since this should be placed in the switch task type.

ok, Added a more complete description.

@SbloodyS SbloodyS added the improvement make more easy to user or prompt friendly label Mar 10, 2026
@SbloodyS SbloodyS added this to the 3.4.2 milestone Mar 10, 2026
@njnu-seafish njnu-seafish requested a review from SbloodyS March 12, 2026 02:10
> In the new version after 3.3.0, the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.
> In legacy versions (3.2.2 and earlier), downstream node B could obtain the OUT type output X of upstream node A without configuring an IN type local variable X.
> In new versions (3.3.0 and later), the logic for obtaining local variables has been modified: downstream node B can only use the OUT type output X of upstream node A if it has configured an IN type local variable X.
> In all versions, for Switch nodes, there is no need to configure an IN type local variable X; you can directly use the OUT type output X from the upstream node A.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> In all versions, for Switch nodes, there is no need to configure an IN type local variable X; you can directly use the OUT type output X from the upstream node A.

We don't need this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need this.

ok, delete it

@njnu-seafish njnu-seafish requested a review from SbloodyS March 12, 2026 10:58
Copy link
Copy Markdown
Member

@SbloodyS SbloodyS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SbloodyS SbloodyS merged commit bf46ddd into apache:dev Mar 16, 2026
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

document improvement make more easy to user or prompt friendly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Doc][Parameter Context] Improvement Parameter passing behavior doc

2 participants