-
Notifications
You must be signed in to change notification settings - Fork 30
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
Cope with defaults #179
Comments
Not sure there should be a Similarly something like |
@mseri thinking about this some more, as it is "only" the validation code for the API responses it would probably be better as
There seems little point having the Python code do default substitution here when the return value isn't going to contain that data. But, only for those fields with an |
If something like
where volume_type is
and then the generator is run the Python code looks like
which then throws a
KeyError
if the value is not passed, which is obviously not the intent when placing an@default
in the definition.I think it should be using
tmp_26.get('volume_type', "Data")[0]
insteadThe text was updated successfully, but these errors were encountered: