Help plugins parameters

[Qmodest]

Self Checks

• 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

i want to parameters type: array ?but it not work and error
parameters:

• name: file_id_or_url
  type: string
  required: false
  label:
  en_US: 文件id或url
  zh_Hans: 文件id或url
  pt_BR: 文件id或url
  human_description:
  en_US: 支持单个字符串、逗号分隔的字符串，或字符串数组；根据related_id或url反向获取文件对象，便于作为文件对象类型参数传递
  zh_Hans: 支持单个字符串、逗号分隔的字符串，或字符串数组；根据related_id或url反向获取文件对象，便于作为文件对象类型参数传递
  pt_BR: 支持单个字符串、逗号分隔的字符串，或字符串数组；根据related_id或url反向获取文件对象，便于作为文件对象类型参数传递
  llm_description: 支持单个字符串、逗号分隔的字符串，或字符串数组；根据related_id或url反向获取文件对象，便于作为文件对象类型参数传递
  form: llm
• name: file_list
  type: array
  required: false

2. Additional context or comments

No response

[dosubot[bot]]

Dify currently does not support generic array types for user-defined plugin parameters in the UI or YAML configuration. Only specific array types like array[tools] (for tool selectors) and FILES (for multiple file uploads) are supported. Generic arrays (such as a list of strings or objects) are not available as selectable parameter types for custom tools, which is why your type: array parameter results in an error. Arrays can be handled at the OpenAPI schema level for certain API requests, but not in the plugin parameter UI or YAML config for custom tools. As a workaround, you can use a comma-separated string and parse it in your plugin logic if you need to accept multiple values. More details are available in this discussion: Does Dify custom tools support array type input parameters?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[keatsyh]

@dosu 1.9.1 Whether it is supported

[simonjhy]

We kindly request that Dify officially allow users to freely use the officially defined and supported data types as interfaces in custom plugins as soon as possible. The current restrictions are severely hindering many users from adopting Dify as a product. Lifting these limitations and allowing users to freely extend the functionality will undoubtedly significantly accelerate the popularity and promotion of Dify. Please do it ASAP !!!!!!!!!!

Official plugin can directly any output node, custom plugin should be approved to use all the data type defined by Dify, right?

dify/web/app/components/workflow/nodes/iteration/use-config.ts

Lines 34 to 44 in 876f48d

const filterInputVar = useCallback((varPayload: Var) => {
return [VarType.array, VarType.arrayString, VarType.arrayBoolean, VarType.arrayNumber, VarType.arrayObject, VarType.arrayFile].includes(varPayload.type)
}, [])

const handleInputChange = useCallback((input: ValueSelector | string, _varKindType: VarKindType, varInfo?: Var) => {
const newInputs = produce(inputs, (draft) => {
draft.iterator_selector = input as ValueSelector || []
draft.iterator_input_type = varInfo?.type || VarType.arrayString
})
setInputs(newInputs)
}, [inputs, setInputs])