We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently the generated server assumes that responses never define headers.
The text was updated successfully, but these errors were encountered:
Seems the generator also ignored responses when multiple entries are defined?
Example operation:
put: tags: ['tweets'] operationId: 'putTweet' summary: 'Send a single tweet.' parameters: - name: 'tweet' in: 'body' description: 'The tweet to post' required: true schema: { '$ref': '#/definitions/Tweet' } responses: '201': description: 'Tweet has been saved.' schema: { '$ref': '#/definitions/Result' } '400': description: 'There are validation error(s).' schema: { '$ref': '#/definitions/Result' }
This result in the following signature being generated for the operation:
type PutTweetHandlerFunc func(PutTweetParams) error
So no mention of the Result struct there.
Result
Sorry, something went wrong.
Assuming this is because there is no code in go-swagger to differentiate between different response codes yet?
go-swagger
I have this for the client on the template-refactor branch, but no such thing for the server yet
526b0f8
No branches or pull requests
Currently the generated server assumes that responses never define headers.
The text was updated successfully, but these errors were encountered: