langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

[PR #396] fix(service/controller): add support for paginated and non-paginated plugin list responses with backward compatibility #489

New Issue
Open
opened 2026-02-16 01:16:07 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 01:16:07 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugin-daemon/pull/396
Author: @homejim
Created: 7/11/2025
Status: 🔄 Open

Base: main ← Head: list_plugin_resp

📝 Commits (1)

  • d965ac1 feat(service/controller): add support for paginated and non-paginated plugin list responses with backward compatibility

📊 Changes

2 files changed (+14 additions, -10 deletions)

View changed files

📝 internal/server/controllers/plugins.go (+5 -4)
📝 internal/service/manage_plugin.go (+9 -6)

📄 Description

… plugin list responses with backward compatibility

Description

Fixes https://github.com/langgenius/dify/issues/22250
During the upgrade process, we encountered an error (reference issue: xxx). I resolved this by introducing a new response_type parameter in the Plugin Daemon.

Fix Details:

  1. Added an optional response_type parameter to the /plugin/{tenantId}/management/list API:
  • If response_type=paged is specified, the endpoint returns a paginated response.
  • Otherwise, it returns the legacy non-paginated format, ensuring backward compatibility with older versions of Dify.
  1. In Dify v1.6.0, the response_type=paged parameter is now included by default when calling this endpoint, aligning it with the updated Plugin Daemon behavior.

Recommended Upgrade Paths:

  • For users who have not yet upgraded:

It's recommended to upgrade Plugin Daemon first, followed by Dify. This ensures a smooth and error-free transition.

  • For users who have already upgraded:

You should first upgrade Dify to v1.6.0 before upgrading Plugin Daemon, to ensure compatibility between components.

Type of Change

  • Bug fix
  • New feature
  • Refactor
  • Performance improvement
  • Other

Essential Checklist

Testing

  • I have tested the changes locally and confirmed they work as expected
  • I have added unit tests where necessary and they pass successfully

Bug Fix (if applicable)

  • I have used GitHub syntax to close the related issue (e.g., Fixes #123 or Closes #123)

Additional Information

Please provide any additional context that would help reviewers understand the changes.

🔄 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-daemon/pull/396 **Author:** [@homejim](https://github.com/homejim) **Created:** 7/11/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `list_plugin_resp` --- ### 📝 Commits (1) - [`d965ac1`](https://github.com/langgenius/dify-plugin-daemon/commit/d965ac178d5eb2d7eab8a894d3841479e8a6bc2d) feat(service/controller): add support for paginated and non-paginated plugin list responses with backward compatibility ### 📊 Changes **2 files changed** (+14 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `internal/server/controllers/plugins.go` (+5 -4) 📝 `internal/service/manage_plugin.go` (+9 -6) </details> ### 📄 Description … plugin list responses with backward compatibility ## Description Fixes https://github.com/langgenius/dify/issues/22250 During the upgrade process, we encountered an error (reference issue: xxx). I resolved this by introducing a new response_type parameter in the Plugin Daemon. **Fix Details:** 1. Added an optional response_type parameter to the /plugin/{tenantId}/management/list API: - If response_type=paged is specified, the endpoint returns a paginated response. - Otherwise, it returns the legacy non-paginated format, ensuring backward compatibility with older versions of Dify. 2. In Dify v1.6.0, the response_type=paged parameter is now included by default when calling this endpoint, aligning it with the updated Plugin Daemon behavior. **Recommended Upgrade Paths:** - **For users who have not yet upgraded:** It's recommended to upgrade Plugin Daemon first, followed by Dify. This ensures a smooth and error-free transition. - **For users who have already upgraded:** You should first upgrade Dify to v1.6.0 before upgrading Plugin Daemon, to ensure compatibility between components. ## Type of Change - [x] Bug fix - [ ] New feature - [ ] Refactor - [ ] Performance improvement - [ ] Other ## Essential Checklist ### Testing - [x] I have tested the changes locally and confirmed they work as expected - [ ] I have added unit tests where necessary and they pass successfully ### Bug Fix (if applicable) - [x] I have used GitHub syntax to close the related issue (e.g., `Fixes #123` or `Closes #123`) ## Additional Information Please provide any additional context that would help reviewers understand the changes. --- <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-16 01:16:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
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-daemon#489
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?