Closed Howe829 closed 4 weeks ago
Hi @Howe829,
thanks for the contribution! The api spec still has an issue, just changing the type object to array is not enough. See https://github.com/langgenius/dify-docs/pull/320
You can test it here: https://editor.swagger.io/
Hi @Howe829,
thanks for the contribution! The api spec still has an issue, just changing the type object to array is not enough. See #320
You can test it here: https://editor.swagger.io/
Hi @perzeuss , I am wondering why we need to add the 'items'? I think the response structure like below is enough.
Hi @Howe829, thanks for the contribution! The api spec still has an issue, just changing the type object to array is not enough. See #320 You can test it here: https://editor.swagger.io/
Hi @perzeuss , I am wondering why we need to add the 'items'? I think the response structure like below is enough.
What you see in the screenshot is just an example response. But the problem is that the schema is invalid, not the example. The schema must define the response type as an array whose elements are of type object.
Hi @Howe829, thanks for the contribution! The api spec still has an issue, just changing the type object to array is not enough. See #320 You can test it here: https://editor.swagger.io/
Hi @perzeuss , I am wondering why we need to add the 'items'? I think the response structure like below is enough.
What you see in the screenshot is just an example response. But the problem is that the schema is invalid, not the example. The schema must define the response type as an array whose elements are of type object.
I think this pr has changed the records type to be 'array'.Could you please comment the changes if there's any problem.
Hi, thanks for the suggestions! The documentation will be updated soon.
The external knowledge api doc have some errors. 1.it should be "retrieval_setting" not "retrival_setting" of the request body.