Update content for boolean, boolean array, and object data type support; refine user input page #640
Conversation
…rt; refine user input page
dosubot
bot
added
the
size:L
There was a problem hiding this comment.
Pull request overview
This PR updates documentation to reflect new data type support (Boolean, Boolean arrays) across multiple node types and refines the User Input page for improved clarity and consistency.
Key changes:
- Adds Boolean data type support documentation to Variable Assigner and Variable Aggregator nodes
- Introduces JSON Code input field type with optional schema validation
- Streamlines descriptions across all affected pages for better readability and consistency
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| en/use-dify/nodes/variable-assigner.mdx | Adds Boolean tab to operation modes section, reformats operation descriptions as bullet points, and moves array operations tip inside the Array tab |
| en/use-dify/nodes/variable-aggregator.mdx | Adds Boolean to the list of supported data types |
| en/use-dify/nodes/user-input.mdx | Updates descriptions for clarity, adds JSON Code input field documentation, reorganizes file processing section with better formatting |
| en/use-dify/nodes/list-operator.mdx | Adds array[boolean] support and removes redundant "Supported Data Types" section |
| en/use-dify/nodes/ifelse.mdx | Minor text clarification for "Contains" operation description |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| You can configure custom input fields in a User Input node to collect information from end users. Each field becomes a variable that can be referenced by downstream nodes. For example, if you add an input field with the variable name `user_name`, you can reference it as `{{user_name}}` throughout the workflow. | ||
|
|
||
| There are seven types of input fields you can choose from to handle different kinds of user input. | ||
| You can configure custom input fields in a User Input node to collect different kinds of user input. Each field becomes a variable that can be referenced by downstream nodes. |
There was a problem hiding this comment.
The original text mentioned that each field "becomes a variable that can be referenced by downstream nodes. For example, if you add an input field with the variable name user_name, you can reference it as {{user_name}} throughout the workflow." This helpful example showing how to reference variables using the {{variable_name}} syntax was removed. Consider keeping this practical example as it helps users understand how to use the variables in their workflows.
| You can configure custom input fields in a User Input node to collect different kinds of user input. Each field becomes a variable that can be referenced by downstream nodes. | |
| You can configure custom input fields in a User Input node to collect different kinds of user input. Each field becomes a variable that can be referenced by downstream nodes. For example, if you add an input field with the variable name `user_name`, you can reference it as `{{user_name}}` throughout the workflow. |
🌐 Multi-language Sync✅ Created sync PR #641 Synced 10 files to cn + jp Both PRs can merge independently. Future commits here will auto-update the sync PR. |
…y, and object data type support; refine user input page (#641) * 🌐 Initial translations for PR #640 Auto-generated translations for documentation changes in PR #640. Last-Processed-Commit: 2309055 Original-PR: #640 Languages: Chinese (zh), Japanese (ja) 🤖 Generated with GitHub Actions * Update variable-assigner.mdx * Update variable-assigner.mdx --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Riskey <36894937+RiskeyL@users.noreply.github.com>
There was a problem hiding this comment.
user input accepts structured data in JSON format as an object, ideal for passing complex, nested data structures into your application. ?
#https://github.com/langgenius/dify/blob/main/web/app/components/base/form/form-scenarios/base/types.ts
|
Hi @JuncusEffusus, thanks for bringing this to our attention! It seems the relevant code hasn't been merged into the main branch yet. We're working on fixing this issue. Thanks again! |
No description provided.