langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #30412] fix(web): enable JSON_OBJECT type support in console UI #32803

New Issue
Closed
opened 2026-02-21 20:52:06 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:52:06 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/30412

State: closed
Merged: Yes

Summary

PR #29053 introduced JSON_OBJECT support for user inputs. It also introduced an optional JSONSchema validation for json object inputs. However, the JSON_OBJECT option is not enabled in chatflow / workflow orchestration page, leading to confusions.

This PR addresses the problem by removing relevant feature flags in frontend code. It also adjusts how the JSONSchema is edited: the original implementation fills the top level properties for the user, while the current implementation only ensures that the type field of JSONSchema is object if the is JSON Schema field is set.

Fix: #29519

Screenshots

Before After
image image

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/30412 **State:** closed **Merged:** Yes --- ## Summary PR #29053 introduced `JSON_OBJECT` support for user inputs. It also introduced an optional JSONSchema validation for json object inputs. However, the `JSON_OBJECT` option is not enabled in chatflow / workflow orchestration page, leading to confusions. This PR addresses the problem by removing relevant feature flags in frontend code. It also adjusts how the JSONSchema is edited: the original implementation fills the top level properties for the user, while the current implementation only ensures that the `type` field of JSONSchema is `object` if the is `JSON Schema` field is set. Fix: #29519 ## Screenshots | Before | After | |--------|-------| | <img width="530" height="613" alt="image" src="https://github.com/user-attachments/assets/8586db41-c620-4eee-bdbd-742ce8440341" /> | <img width="545" height="605" alt="image" src="https://github.com/user-attachments/assets/df3a5414-ed09-4248-b62d-458f053cf33b" /> | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:52:06 -05:00
yindo closed this issue 2026-02-21 20:52:06 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
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#32803
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?