[PR #23289] Fix: incorrect array element validation in SegmentType #30226

Closed
opened 2026-02-21 20:47:05 -05:00 by yindo · 0 comments
Owner

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

State: closed
Merged: Yes


Fixed a bug in SegmentType._validate_array where
all([...]) for i in value was used incorrectly.
The code always returned True because it produced
a list of truthy values (e.g., [[True], [False]]), causing all()
to succeed regardless of element validity.
Now replaced with a correct generator expression.

Added tests to ensure invalid elements are properly
detected when using ArrayValidation.ALL.

Fixed a typo and removed one line of unused code.

Signed-off-by: Yongtao Huang yongtaoh2022@gmail.com

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

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/23289 **State:** closed **Merged:** Yes --- Fixed a bug in `SegmentType._validate_array` where `all([...]) for i in value` was used incorrectly. The code always returned True because it produced a list of truthy values (e.g., `[[True], [False]]`), causing `all()` to succeed regardless of element validity. Now replaced with a correct generator expression. Added tests to ensure invalid elements are properly detected when using `ArrayValidation.ALL`. Fixed a typo and removed one line of unused code. Signed-off-by: Yongtao Huang <yongtaoh2022@gmail.com> > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 2. Ensure there is an associated issue and you have been assigned to it > 3. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> ## 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:47:05 -05:00
yindo closed this issue 2026-02-21 20:47:05 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#30226