Open Zuruckt opened 1 year ago
Oof, thanks for the screenshots, but I also need to see the code snippets (the docblocks/attributes) to understand. Also not sure if your question I about Try It Out, response calls or something else.
@shalvah , @Zuruckt I'm facing the same issue, is it fixed? It's with Try It Out response calls
@shalvah Any updates ?!
Oof, thanks for the screenshots, but I also need to see the code snippets (the docblocks/attributes) to understand. Also not sure if your question I about Try It Out, response calls or something else.
Oh sorry, I didn't see your response until @Mohdk911 brought back this issue. I was in a hurry in the time so I ended up doing some other method for this problem so I don't have the code anymore. But I still think it's a relevant issue and I can try to make a reproduction case later this week.
@Zuruckt Thank you very much. Could you please provide me with a workaround to resolve this issue? I attempted to utilize "No-example," but it no longer recognizes the uploaded image as an UploadedFile instance. Instead, it reads the image as an empty array.
* @bodyParam image_file file image required No-example
* Image file
@Zuruckt Is there any update about this issue ?!
Scribe version
4.22.0 | Laravel 10.x
Your question
When using
file
type, the content type is changed tomultipart/form-data
as expected. This, however make me unable to use theobject
type, has the format it sends the parameters is modified.Is there something I'm missing here to use both
object/arrays
andfile
types in the same requisition? When I remove the file/content-type it works fineDocs