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
unmarshal bug in 4.7.(0|1) #163
Comments
My API responded with 200, here's an example JSON body
|
@cbarraford could you post your swagger spec as well please? |
@sjaensch sorry, our API is private and I can't disclose it. Sorry! |
@cbarraford unfortunately then you'll have to either create a reduced test case or do some debugging on your own. What I can say from the stack trace is that it has something to do with one of the properties for which the value is |
Yeah, trying to debug on my own. Heres what i got so far... the func But then we don't handle |
Agreed, we should handle a spec not being available gracefully. Working on a fix. |
created a PR with the fix, #164 |
I've confirmed that we don't get the following error when i downgrade from 4.7.0 (or 4.7.1) to 4.6.1.
The text was updated successfully, but these errors were encountered: