-
Notifications
You must be signed in to change notification settings - Fork 98
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
panic: interface conversion: interface {} is nil, not string #47
Comments
Update, if I load the swagger spec (JSON) into SwaggerHub and then download it as a Resolved YAML file I hit #40 so I wonder if it isn't somehow related to that. If I download it as an Unresolved YAML file I get this same error here. |
Howdy @bhechinger! I've just pushed a commit to master that provides a much cleaner error message. From running this spec through the tool, it seems you're missing a
I'm looking through the spec and this field may not be required if the field is Stay tuned! |
It's not my spec but if you think I should badger the authors about that (if it's actually wrong) then I certainly will. :) |
Woo! That fixed it, thanks man!! |
No problem! I think I introduced this bug with some other recent updates, so felt obligated to knock it out. Please holler if you run into any other funk! |
I'm fetching this swagger spec file: https://esi.tech.ccp.is/latest/swagger.json?datasource=tranquility
When I run openapi2proto against it I get an error (and massive stacktrace). Not sure what's going on as that's not completely descriptive to me.
The text was updated successfully, but these errors were encountered: