You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title=>"xxx API Dokumentation"auth.enabled=>trueauth.default=>trueauth.name=>"Authorization"logo=>"logo.svg"examples.faker_seed=>1234strategies.headers=>added['override',['Content-Type'=>'application/json','Accept'=>'application/json','im-client-type'=>'app','im-app-version'=>'2024.08.14','im-device-id'=>'id123',],]: removed[
'override',['Content-Type'=>'application/json','Accept'=>'application/json',],]
What happened?
The Command generates the postman collection and I want to upload it to the postman api using the put api, but the request gets rejected because of a validation failure.
The problem is following json part in a formdata request:
which is generated from following rules of a form request:
public function rules(): array
{
return [
'size' => ['required', 'numeric', 'min:0'],
];
}
Postman rejects the file, because the form data is set to type "text", but the value is an integer. Can the generation of the collection respect the type? I think the change needs to be made in the PostmanCollectionWriter in getFormDataParams, if its not type file always cast the value to a string?
Scribe version
4.37.1
PHP version
8.3.9
Framework
Laravel
Framework version
11.20.0
Scribe config
What happened?
The Command generates the postman collection and I want to upload it to the postman api using the put api, but the request gets rejected because of a validation failure.
The problem is following json part in a formdata request:
which is generated from following rules of a form request:
Postman rejects the file, because the form data is set to type "text", but the value is an integer. Can the generation of the collection respect the type? I think the change needs to be made in the PostmanCollectionWriter in getFormDataParams, if its not type file always cast the value to a string?
Docs
The text was updated successfully, but these errors were encountered: