The custom node's return is always forced to be dumped as a string #5890

Closed
opened 2026-02-21 18:13:05 -05:00 by yindo · 1 comment
Owner

Originally created by @kenyo3023 on GitHub (Oct 1, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • 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.

Make the node (built-in tool, json_parse, etc) no longer forced to dump as a string.

ex 1: built-in tool

pr-json-before-builtin

ex 2: json parse

pr-json-before

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 @kenyo3023 on GitHub (Oct 1, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [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. Make the node (built-in tool, json_parse, etc) no longer forced to dump as a string. ### ex 1: built-in tool ![pr-json-before-builtin](https://github.com/user-attachments/assets/0778c0b9-53a9-421f-8372-fd2413bc7f9b) ### ex 2: json parse ![pr-json-before](https://github.com/user-attachments/assets/b0bfd90d-9eff-43ef-a1fb-d247b5913ef8) ### 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 🐞 bug label 2026-02-21 18:13:05 -05:00
yindo closed this issue 2026-02-21 18:13:05 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Nov 1, 2024):

Hi, @kenyo3023! I'm helping the Dify team manage their backlog and am marking this issue as stale.

You raised a request for the custom node's return value to not be forced to be dumped as a string, especially for built-in tools and JSON parsing. You also expressed interest in contributing to this feature, but there haven't been any additional comments or developments since then.

Could you please let us know if this issue is still relevant to the latest version of the Dify repository? If it is, feel free to comment here to keep it open. Otherwise, you can close the issue yourself, or it will be automatically closed in 7 days. Thank you!

@dosubot[bot] commented on GitHub (Nov 1, 2024): Hi, @kenyo3023! I'm helping the Dify team manage their backlog and am marking this issue as stale. You raised a request for the custom node's return value to not be forced to be dumped as a string, especially for built-in tools and JSON parsing. You also expressed interest in contributing to this feature, but there haven't been any additional comments or developments since then. Could you please let us know if this issue is still relevant to the latest version of the Dify repository? If it is, feel free to comment here to keep it open. Otherwise, you can close the issue yourself, or it will be automatically closed in 7 days. Thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5890