langgenius/dify-plugin-sdks
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-sdks.git synced 2026-07-22 02:15:22 -04:00
Code Issues 58 Packages Projects Releases 10 Wiki Activity

[PR #197] [MERGED] feat: add filename support to multi-modal prompt messages #213

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

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugin-sdks/pull/197
Author: @laipz8200
Created: 8/29/2025
Status: ✅ Merged
Merged: 8/29/2025
Merged by: @Yeuoly

Base: main ← Head: feat/support-filename-in-multi-modal-prompt

📝 Commits (2)

  • ab607aa feat: add filename support to multi-modal prompt messages
  • e8aa8d4 docs(README.md): update version binding

📊 Changes

2 files changed (+2 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)
📝 python/dify_plugin/entities/model/message.py (+1 -0)

📄 Description

Summary

This PR adds filename support to multi-modal prompt messages by introducing a filename field to the MultiModalPromptMessageContent class. This change aligns the SDK with the main Dify repository implementation (PR langgenius/dify#24777).

Changes

  • Added filename field (default: empty string) to MultiModalPromptMessageContent class in python/dify_plugin/entities/model/message.py
  • The filename field is optional and defaults to an empty string for backward compatibility
  • Inherited by all multi-modal content types (Image, Video, Audio, Document)

Testing

  • Verified field is properly added to the class
  • Confirmed backward compatibility with default empty string value

Closes #196

Pull Request Checklist

Compatibility Check

  • I have checked whether this change affects the backward compatibility of the plugin declared in README.md
  • I have checked whether this change affects the forward compatibility of the plugin declared in README.md
  • If this change introduces a breaking change, I have discussed it with the project maintainer and specified the release version in the README.md
  • I have described the compatibility impact and the corresponding version number in the PR description
  • I have checked whether the plugin version is updated in the README.md

Compatibility Impact: This change is fully backward compatible. The new filename field defaults to an empty string, so existing code will continue to work without modification.

Available Checks

  • Code has passed local tests
  • Relevant documentation has been updated (if necessary) - Field includes proper description

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugin-sdks/pull/197 **Author:** [@laipz8200](https://github.com/laipz8200) **Created:** 8/29/2025 **Status:** ✅ Merged **Merged:** 8/29/2025 **Merged by:** [@Yeuoly](https://github.com/Yeuoly) **Base:** `main` ← **Head:** `feat/support-filename-in-multi-modal-prompt` --- ### 📝 Commits (2) - [`ab607aa`](https://github.com/langgenius/dify-plugin-sdks/commit/ab607aa97271f00f6ef91536baf6ed22d50e245a) feat: add filename support to multi-modal prompt messages - [`e8aa8d4`](https://github.com/langgenius/dify-plugin-sdks/commit/e8aa8d4c730a368e682b63944724beb9bc6f88bb) docs(README.md): update version binding ### 📊 Changes **2 files changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) 📝 `python/dify_plugin/entities/model/message.py` (+1 -0) </details> ### 📄 Description ## Summary This PR adds filename support to multi-modal prompt messages by introducing a `filename` field to the `MultiModalPromptMessageContent` class. This change aligns the SDK with the main Dify repository implementation (PR langgenius/dify#24777). ### Changes - Added `filename` field (default: empty string) to `MultiModalPromptMessageContent` class in `python/dify_plugin/entities/model/message.py` - The filename field is optional and defaults to an empty string for backward compatibility - Inherited by all multi-modal content types (Image, Video, Audio, Document) ### Testing - Verified field is properly added to the class - Confirmed backward compatibility with default empty string value Closes #196 ## Pull Request Checklist ### Compatibility Check - [x] I have checked whether this change affects the **backward compatibility** of the plugin declared in `README.md` - [x] I have checked whether this change affects the **forward compatibility** of the plugin declared in `README.md` - [ ] If this change introduces a breaking change, I have discussed it with the project maintainer and specified the release version in the `README.md` - [x] I have described the compatibility impact and the corresponding version number in the PR description - [ ] I have checked whether the plugin version is updated in the `README.md` **Compatibility Impact**: This change is fully backward compatible. The new `filename` field defaults to an empty string, so existing code will continue to work without modification. ### Available Checks - [x] Code has passed local tests - [x] Relevant documentation has been updated (if necessary) - Field includes proper description 🤖 Generated with [Claude Code](https://claude.ai/code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 21:16:15 -05:00
yindo closed this issue 2026-02-15 21:16:15 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
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-plugin-sdks#213
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?