-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
Assignment to entry in nil map with @Header all #1082
Comments
This should be fixed in here #1066, and it will go with the next release (a few days far away). Please build swag using the latest version from master and let us know. |
@microphoneabuser any updates here? |
@ubogdan No, panic still occurs. |
ubogdan
added a commit
that referenced
this issue
Dec 23, 2021
ubogdan
added a commit
that referenced
this issue
Dec 23, 2021
@microphoneabuser this has been fixed and released with v1.7.7. |
@ubogdan It's working fine now, thank you! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using
@Header all
instead of explicitly writing response codes, panic occurs.Code used:
Result:
But if i use:
@Header 200,400,404,500 {string} X-Request-ID "Some description"
it works fine.The problem is in operation.go (*Operation).ParseResponseHeaderComment:
To fix it, we just need to initialize
response.Headers
beforeresponse.Headers[headerKey] = header
:To Reproduce
Use
@Header all
The text was updated successfully, but these errors were encountered: