feat: support reset_on_change for tool parameters - #378
Open
zyqzyq wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes langgenius/dify#40180
Summary
This PR adds
reset_on_changesupport to the Python SDK'sToolParametermodel.Plugin developers can declare sibling parameters that should reset the current parameter to its default or empty value when changed:
The field defaults to an empty list, preserving the behavior of existing plugin declarations.
Unit tests have been added to verify:
reset_on_changefrom a tool parameter declarationCompatibility Impact
This is an additive and backward-compatible change. Existing plugin declarations do not need to define
reset_on_changeand will continue to work as before.Plugins using
reset_on_changerequire compatible Dify platform and plugin daemon versions. This change does not introduce a breaking schema change, so no plugin declaration version or README version update is required.Pull Request Checklist
Thank you for your contribution! Before submitting your PR, please make sure you have completed the following checks:
Compatibility Check
README.mdREADME.mdREADME.md(Not applicable: this is not a breaking change)README.md(No version update is required)Available Checks
just buildhas passed