Implement required:false
for parameter of type File
#1154
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #1151
The Swagger/OpenAPI spec indicates that
required: false
can be used to make any API parameters optional. The current implementation of go-swagger completely ignores this when generating theBindRequest
for parameters of typefile
. The result is that allfile
parameters are mandatory and clients that omit any results in a HTTP 500 returned by the middleware layer.This pull request makes a change to the
parameter.gotmpl
template to handle nullablefile
parameters.Here's the generated output for
required: true
(current behaviour):Here's the generated output for
required: false
with this new template: