-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Minor issues with field2choices #198
Labels
Comments
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think that in marshmallow swagger, some pathological cases are not handled the best way.
This
produces
which is wrong. Admittedly, the field declaration does not make much sense.
Also
produces
which is wrong too. This field declaration is a big dodgy as well.
Those are corner cases that might happen, perhaps, in some complex inheritance scenarios.
apispec should at least return the correct output. Maybe raising a warning is out of scope, as if we engage in consistency validation in apispec, this could end up being a lot of work.
No time and interest to address this right now but I thought I'd leave a note here.
The text was updated successfully, but these errors were encountered: