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
The text was updated successfully, but these errors were encountered:
e-nikolov
changed the title
Chai doesn't work with go1.18 due to changes in runtime.CallersFrames
Chai doesn't work with go1.18 due to changes in runtime.FuncForPC
Apr 6, 2022
e-nikolov
changed the title
Chai doesn't work with go1.18 due to changes in runtime.FuncForPC
Swagger spec generation doesn't work with go1.18 due to changes in runtime.FuncForPC
Apr 6, 2022
The request/response json.Unmarshal/json.Marshal works at runtime with go1.18, but the swagger generation fails during the static code analysis.
As a workaround, go1.18beta2 can be used at compile time for the generation of the swagger spec and go1.18 can be used at runtime for the generic handlers.
A more robust approach should be looked into for linking a handler function that is used at runtime with the comment that contains its extended swagger annotations. Perhaps the Delve debugger can help.
Something changed between go1.18beta2 and go1.18 resulting in
runtime.FuncForPC(ptr).FileLine()
returning<autogenerated>
instead of a file namegolang/go#51774
The text was updated successfully, but these errors were encountered: