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

OpenApi 3.1.0 ArrayType is recognized as StringType unexpectly #4314

New Issue
Closed
opened 2026-02-21 18:05:42 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:05:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @forrestsocool on GitHub (Jun 28, 2024).

Originally assigned to: @laipz8200 on GitHub.

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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.11

Cloud or Self Hosted

Cloud

Steps to reproduce

Import this openapi schema as custom tool, add it into a workflow later, the "article_ids" parameter of ApiInsertArticleInsert is recognized as StringType instead of ArrayType[StringType ] (which Coze workflow can recognize correctly, though it only support 3.0.0 openApi schema, u can convert it ):

the openapi 3.1.0 schema generated by LiteStar

openapi (4).json

✔️ Expected Behavior

type of paramerter article_ids should be list[str]

❌ Actual Behavior

type of paramerter article_ids is str

Originally created by @forrestsocool on GitHub (Jun 28, 2024). Originally assigned to: @laipz8200 on GitHub. ### 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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.11 ### Cloud or Self Hosted Cloud ### Steps to reproduce Import this openapi schema as custom tool, add it into a workflow later, the "article_ids" parameter of ApiInsertArticleInsert is recognized as StringType instead of ArrayType[StringType ] (which Coze workflow can recognize correctly, though it only support 3.0.0 openApi schema, u can convert it ): the openapi 3.1.0 schema generated by LiteStar [openapi (4).json](https://github.com/user-attachments/files/16032615/openapi.4.json) ### ✔️ Expected Behavior type of paramerter article_ids should be list[str] ### ❌ Actual Behavior type of paramerter article_ids is str
yindo added the 💪 enhancement label 2026-02-21 18:05:42 -05:00
yindo closed this issue 2026-02-21 18:05:42 -05:00
yindo commented 2026-02-21 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 28, 2024):

The issue with the article_ids parameter being recognized as StringType instead of ArrayType[StringType] in Dify version 0.6.11 is due to the _get_tool_parameter_type method in the ApiBasedToolSchemaParser class not handling array types. This method currently only checks for integer, number, boolean, and string types, and defaults to STRING for any other type.

Here is the relevant part of the code:

@staticmethod
def _get_tool_parameter_type(parameter: dict) -> ToolParameter.ToolParameterType:
    parameter = parameter or {}
    typ = None
    if 'type' in parameter:
        typ = parameter['type']
    elif 'schema' in parameter and 'type' in parameter['schema']:
        typ = parameter['schema']['type']
    
    if typ == 'integer' or typ == 'number':
        return ToolParameter.ToolParameterType.NUMBER
    elif typ == 'boolean':
        return ToolParameter.ToolParameterType.BOOLEAN
    elif typ == 'string':
        return ToolParameter.ToolParameterType.STRING

Since the method does not check for array type, it defaults to STRING. To fix this, you would need to modify the _get_tool_parameter_type method to handle array types appropriately [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jun 28, 2024): <!-- Answer --> The issue with the `article_ids` parameter being recognized as `StringType` instead of `ArrayType[StringType]` in Dify version 0.6.11 is due to the `_get_tool_parameter_type` method in the `ApiBasedToolSchemaParser` class not handling array types. This method currently only checks for `integer`, `number`, `boolean`, and `string` types, and defaults to `STRING` for any other type. Here is the relevant part of the code: ```python @staticmethod def _get_tool_parameter_type(parameter: dict) -> ToolParameter.ToolParameterType: parameter = parameter or {} typ = None if 'type' in parameter: typ = parameter['type'] elif 'schema' in parameter and 'type' in parameter['schema']: typ = parameter['schema']['type'] if typ == 'integer' or typ == 'number': return ToolParameter.ToolParameterType.NUMBER elif typ == 'boolean': return ToolParameter.ToolParameterType.BOOLEAN elif typ == 'string': return ToolParameter.ToolParameterType.STRING ``` Since the method does not check for `array` type, it defaults to `STRING`. To fix this, you would need to modify the `_get_tool_parameter_type` method to handle `array` types appropriately <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/utils/parser.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jul 1, 2024):

Our tool currently doesn't support array-type parameters, we might add this feature in the future.

@laipz8200 commented on GitHub (Jul 1, 2024): Our tool currently doesn't support array-type parameters, we might add this feature in the future.
yindo commented 2026-02-21 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@qdaoming commented on GitHub (Jul 22, 2024):

Our tool currently doesn't support array-type parameters, we might add this feature in the future.

@laipz8200 This is an important missing feature. Do you know when it will be implemented?

@qdaoming commented on GitHub (Jul 22, 2024): > Our tool currently doesn't support array-type parameters, we might add this feature in the future. @laipz8200 This is an important missing feature. Do you know when it will be implemented?
yindo commented 2026-02-21 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jul 27, 2024):

Our tool currently doesn't support array-type parameters, we might add this feature in the future.

@laipz8200 This is an important missing feature. Do you know when it will be implemented?

Since not all models have the capability to generate complex structured parameters, this feature is not a high priority for our team. However, you are welcome to try implementing it yourself.

@laipz8200 commented on GitHub (Jul 27, 2024): > > Our tool currently doesn't support array-type parameters, we might add this feature in the future. > > @laipz8200 This is an important missing feature. Do you know when it will be implemented? Since not all models have the capability to generate complex structured parameters, this feature is not a high priority for our team. However, you are welcome to try implementing it yourself.
yindo commented 2026-02-21 18:05:43 -05:00
Author
Owner
Copy Link
Copy Source

@qdaoming commented on GitHub (Aug 4, 2024):

Our tool currently doesn't support array-type parameters, we might add this feature in the future.

@laipz8200 This is an important missing feature. Do you know when it will be implemented?

Since not all models have the capability to generate complex structured parameters, this feature is not a high priority for our team. However, you are welcome to try implementing it yourself.

The input of tools can be from several sources, not only from LLM.
As said above, coze workflow works well for it.
If I can find available time, I might check this issue.

@qdaoming commented on GitHub (Aug 4, 2024): > > > Our tool currently doesn't support array-type parameters, we might add this feature in the future. > > > > > > @laipz8200 This is an important missing feature. Do you know when it will be implemented? > > Since not all models have the capability to generate complex structured parameters, this feature is not a high priority for our team. However, you are welcome to try implementing it yourself. The input of tools can be from several sources, not only from LLM. As said above, coze workflow works well for it. If I can find available time, I might check this issue.
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 💪 enhancement
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#4314
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?