fredbi

The yaml parser scans SecurityDefinitions tags, as well as Info/Extensions blocks Maybe you defined invalid SecurityDefinitions ?

This has been a missing feature so far: string binary in formData. The fix on the server side is quite straightforward. However, I could see the same kind of problem...

No this won't work because the binding occurs with a string. I quickly made the fix but testing will take some time.

Anyway, the best way to send a file is to tell the spec this is a file type. And this one works fine with the io.ReadCloser well implemented.

@casualjim : even though I agree that the OP _should_ use `type: file` for this use case, I don't see it explicitly disallowed by the swagger 2.0 spec. I know...

I think that we may go with `io.ReadCloser` for form params, and that a way to fool-proof the generator for other params with this format would be just to ignore...

Adding `binary` is formally allowed by the spec, but of no practical use. In the go-swagger implementation, we use the very definition of `type: string format binary` as a _sequence...

@cezarykluczynski you are welcome to ask questions at https://github.com/go-swagger/go-swagger/issues. At go-openapi/ & go-swagger we try to abide as much as possible by the jsonschema v4 definition of what a $ref...

See https://github.com/go-swagger/go-swagger/issues/2105 https://github.com/go-swagger/go-swagger/blob/master/fixtures/goparsing/classification/operations/noparams.go#L28-L33 The swagger way is to use form-data for files. For binary, I don't know. Maybe you could share a minimal bit of code that builds so we...

You are using relative path to modules. I found in your code: ``` import ( "crypto/tls" "e-food/api/restapi/operations" "e-food/clients" "e-food/handlers" "e-food/pkg/dao" "e-food/pkg/utils" "github.com/go-openapi/errors" "github.com/go-openapi/runtime" "github.com/google/uuid" "github.com/rs/cors" "net/http" ) ``` That is...