[PR #26388] fix(plugins): The endpoint form of the extension plugin is missing th… #31415

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

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

State: open
Merged: No


…e input field.

The toolCredentialToFormSchemas function in web/app/components/tools/utils/to-form-schema.ts was not correctly mapping the type property for tool credentials. This resulted in boolean fields not being rendered as checkboxes in the plugin's endpoint form.

This commit adds the type mapping to the function, ensuring that all form fields, including booleans, are rendered correctly.

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

try #26344

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/26388 **State:** open **Merged:** No --- …e input field. The `toolCredentialToFormSchemas` function in `web/app/components/tools/utils/to-form-schema.ts` was not correctly mapping the `type` property for tool credentials. This resulted in boolean fields not being rendered as checkboxes in the plugin's endpoint form. This commit adds the type mapping to the function, ensuring that all form fields, including booleans, are rendered correctly. > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. 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. --> try #26344 ## 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:49: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#31415