[PR #4818] fix 'NoneType' and new ContentType supported. #24655

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

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

State: closed
Merged: Yes


Description

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.

Fixes # (issue)

Type of Change

Please delete options that are not relevant.

  • [ x ] Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update, included: Dify Document
  • [ x ] Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
  • Dependency upgrade

How Has This Been Tested?

image

image

image

Suggested Checklist:

  • [ x ] I have performed a self-review of my own code
  • [ x ] I have commented my code, particularly in hard-to-understand areas
  • [ x ] My changes generate no new warnings
  • [ x ] I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
  • optional I have made corresponding changes to the documentation
  • optional I have added tests that prove my fix is effective or that my feature works
  • optional New and existing unit tests pass locally with my changes
**Original Pull Request:** https://github.com/langgenius/dify/pull/4818 **State:** closed **Merged:** Yes --- # Description 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. Fixes # (issue) ## Type of Change Please delete options that are not relevant. - [ x ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [ x ] Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement - [ ] Dependency upgrade # How Has This Been Tested? <img width="437" alt="image" src="https://github.com/langgenius/dify/assets/1235434/fac31d53-6ae1-40a7-95e0-8e61ac8b3eca"> ![image](https://github.com/langgenius/dify/assets/1235434/919abcae-4396-45ed-973a-0fa816d2b224) ![image](https://github.com/langgenius/dify/assets/1235434/4550065c-97fb-4f0d-a687-dd7b81893ea8) # Suggested Checklist: - [ x ] I have performed a self-review of my own code - [ x ] I have commented my code, particularly in hard-to-understand areas - [ x ] My changes generate no new warnings - [ x ] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods - [ ] `optional` I have made corresponding changes to the documentation - [ ] `optional` I have added tests that prove my fix is effective or that my feature works - [ ] `optional` New and existing unit tests pass locally with my changes
yindo added the pull-request label 2026-02-21 20:23:25 -05:00
yindo closed this issue 2026-02-21 20:23:25 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#24655