langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

The function 【_get_runtime_parameters】 is not yet implemented; it is only a placeholder and currently cannot retrieve user-defined parameters related to the workflow runtime. #685

New Issue
Closed
opened 2026-02-16 10:20:11 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @HnBigVolibear on GitHub (Oct 2, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

The function _get_runtime_parameters（which is in the file: ..site-packages\dify_plugin\interfaces\tool__init__.py） is not yet implemented; it is only a placeholder and currently cannot retrieve user-defined parameters related to the workflow runtime.
`def _get_runtime_parameters(self) -> list[ToolParameter]:
"""
get the runtime parameters of the tool

    :return: the runtime parameters
    """
    return []`

The reason for this requirement is that I have encountered situations where my plugin needs to retrieve a large number of user-defined parameters. For example, the user creates multiple parameters in the start node for integrating with third-party interfaces, and my plugin also needs to access these parameters. However, if all the required input parameters for the plugin are configured in the tool's YAML configuration file, the user would have to manually select and fill in each corresponding parameter every time they use my plugin. This process is very tedious and error-prone. Therefore, I hope to directly retrieve all the initial user-defined input parameters from the start node through the _get_runtime_parameters function. Alternatively, are there any other better methods to directly access them?

I earnestly hope the official team will enhance the functionality by properly implementing the _get_runtime_parameters function, instead of leaving it as a mere placeholder. Your attention to this would be greatly appreciated!

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @HnBigVolibear on GitHub (Oct 2, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. The function _get_runtime_parameters（which is in the file: ..site-packages\dify_plugin\interfaces\tool\__init__.py） is not yet implemented; it is only a placeholder and currently cannot retrieve user-defined parameters related to the workflow runtime. `def _get_runtime_parameters(self) -> list[ToolParameter]: """ get the runtime parameters of the tool :return: the runtime parameters """ return []` The reason for this requirement is that I have encountered situations where my plugin needs to retrieve a large number of user-defined parameters. For example, the user creates multiple parameters in the start node for integrating with third-party interfaces, and my plugin also needs to access these parameters. However, if all the required input parameters for the plugin are configured in the tool's YAML configuration file, the user would have to manually select and fill in each corresponding parameter every time they use my plugin. This process is very tedious and error-prone. Therefore, I hope to directly retrieve all the initial user-defined input parameters from the start node through the _get_runtime_parameters function. Alternatively, are there any other better methods to directly access them? I earnestly hope the official team will enhance the functionality by properly implementing the _get_runtime_parameters function, instead of leaving it as a mere placeholder. Your attention to this would be greatly appreciated! ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the enhancement label 2026-02-16 10:20:11 -05:00
yindo closed this issue 2026-02-16 10:20:11 -05:00
yindo commented 2026-02-16 10:20:11 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 19, 2025):

Hi, @HnBigVolibear. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary

  • You reported that the _get_runtime_parameters function in dify_plugin is currently a placeholder.
  • The function does not support retrieving user-defined workflow runtime parameters.
  • You requested proper implementation to allow plugins to access multiple user-defined inputs from the start node.
  • You expressed interest in contributing to this feature.
  • There has been no further activity or comments on this issue.

Next Steps

  • Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 19, 2025): Hi, @HnBigVolibear. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary** - You reported that the `_get_runtime_parameters` function in `dify_plugin` is currently a placeholder. - The function does not support retrieving user-defined workflow runtime parameters. - You requested proper implementation to allow plugins to access multiple user-defined inputs from the start node. - You expressed interest in contributing to this feature. - There has been no further activity or comments on this issue. **Next Steps** - Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#685
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?