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 #24944] feat: LLM prompt Jinja2 template now support more variables #30861

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

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

State: closed
Merged: Yes

Fixes #24945

Summary

This pull request updates the logic for filtering input variables in the LLM node configuration panel to support a wider range of variable types and improves how variable filtering is applied based on UI state.

Improvements to variable filtering:

  • Expanded the filterJinja2InputVar function in use-config.ts to include additional variable types such as arrayBoolean, arrayObject, object, array, and boolean, allowing for more flexible prompt configuration.

UI logic enhancement:

  • Updated the Panel component in panel.tsx to conditionally use filterJinja2InputVar or filterInputVar for filtering variables, depending on the isShowVars state, ensuring that the correct filtering logic is applied in different UI scenarios.

Screenshots

Before After
... ...

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/24944 **State:** closed **Merged:** Yes --- Fixes #24945 ## Summary This pull request updates the logic for filtering input variables in the LLM node configuration panel to support a wider range of variable types and improves how variable filtering is applied based on UI state. **Improvements to variable filtering:** * Expanded the `filterJinja2InputVar` function in `use-config.ts` to include additional variable types such as `arrayBoolean`, `arrayObject`, `object`, `array`, and `boolean`, allowing for more flexible prompt configuration. **UI logic enhancement:** * Updated the `Panel` component in `panel.tsx` to conditionally use `filterJinja2InputVar` or `filterInputVar` for filtering variables, depending on the `isShowVars` state, ensuring that the correct filtering logic is applied in different UI scenarios. ## Screenshots | Before | After | |--------|-------| | ... | ... | ## 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:48:22 -05:00
yindo closed this issue 2026-02-21 20:48:22 -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#30861
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?