langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-23 04:55:28 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Number Parameter Not Visible and Secret Input Lacks Masking #12090

New Issue
Closed
opened 2026-02-21 19:05:43 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:05:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @jaguarliuu on GitHub (Mar 25, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When developing my Dify plugin, I defined two parameters:

  • A number type parameter
  • A secret-input type parameter

Here is config yaml:

 - name: port
    type: number
    required: true
    form: form
    min: 1
    max: 65535
    label:
      en_US: Database port
      zh_Hans: 数据库端口
      pt_BR: Database port
    human_description:
  - name: password
    type: secret-input
    required: true
    form: form
    label:
      en_US: Password
      zh_Hans: 密码
      pt_BR: Password
    human_description:
      en_US: Password

However, during plugin usage I'm observing two issues:

  • The number type parameter is not being displayed in the UI
  • The secret-input parameter isn't masked (no *** protection) when entered

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @jaguarliuu on GitHub (Mar 25, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When developing my Dify plugin, I defined two parameters: - A number type parameter - A secret-input type parameter Here is config yaml: ```yaml - name: port type: number required: true form: form min: 1 max: 65535 label: en_US: Database port zh_Hans: 数据库端口 pt_BR: Database port human_description: - name: password type: secret-input required: true form: form label: en_US: Password zh_Hans: 密码 pt_BR: Password human_description: en_US: Password ``` However, during plugin usage I'm observing two issues: - The number type parameter is not being displayed in the UI - The secret-input parameter isn't masked (no *** protection) when entered ![Image](https://github.com/user-attachments/assets/caeed95f-44c1-482e-a61d-92bd0857ba0d) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 buggood first issue labels 2026-02-21 19:05:43 -05:00
yindo closed this issue 2026-02-21 19:05:43 -05:00
yindo commented 2026-02-21 19:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 25, 2025):

For the issues you're experiencing with the Dify UI:

  1. Number Type Parameter Not Visible: Ensure that the YAML configuration for the number type parameter is correctly set. The configuration you provided seems correct, but there might be a known issue with the rendering of number type parameters in Dify version 1.1.0. Specifically, there is a known issue where the frontend uses base 1000 instead of base 1024 for certain display formats, but this should not affect visibility [1]. Double-check the YAML configuration and ensure there are no indentation or syntax errors.

  2. Secret-Input Parameter Not Masked: The expected behavior for secret-input type parameters is that they should be masked on the frontend and encrypted on the backend [2]. If the input is not being masked, it might be a bug in the current version. Verify that the parameter type is correctly set to secret-input in your YAML configuration, as it appears to be. If the issue persists, it may require further investigation or a potential update to the platform.

If these issues continue, consider checking for any updates or patches that might address these problems in the Dify repository.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 25, 2025): <!-- Answer --> For the issues you're experiencing with the Dify UI: 1. **Number Type Parameter Not Visible**: Ensure that the YAML configuration for the number type parameter is correctly set. The configuration you provided seems correct, but there might be a known issue with the rendering of number type parameters in Dify version 1.1.0. Specifically, there is a known issue where the frontend uses base 1000 instead of base 1024 for certain display formats, but this should not affect visibility <sup>[[1]](https://github.com/langgenius/dify/issues/13789)</sup>. Double-check the YAML configuration and ensure there are no indentation or syntax errors. 2. **Secret-Input Parameter Not Masked**: The expected behavior for secret-input type parameters is that they should be masked on the frontend and encrypted on the backend <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/tools/quick-tool-integration.md)</sup>. If the input is not being masked, it might be a bug in the current version. Verify that the parameter type is correctly set to `secret-input` in your YAML configuration, as it appears to be. If the issue persists, it may require further investigation or a potential update to the platform. If these issues continue, consider checking for any updates or patches that might address these problems in the Dify repository. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/72aa07a4-ac05-4a48-ad11-11c7400b4de1?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label good first issue 🐞 bug
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#12090
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?