-
Notifications
You must be signed in to change notification settings - Fork 301
Inflect component attributes when using the OpenAPI SchemaGenerator #967
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
Comments
Hey @sliverc, I would like to work on this. Can you guide me a bit so that I can get started ? |
When When looking quickly at the code it seems that the field name here, here and here needs to be formatted with @SwarajBaral |
@sliverc If all that's needed is formatting field.field_name on those lines I'd love to start contributing with that. |
@sha016 Yes as far as I see is formatting field name enough + adjusting the tests. Feel free to give it a try. |
@sliverc I've made those changes and ran tests. The tests fail because the changes that are applied don't match to the last snapshot if I'm reading this right:
When I run |
@sliverc Yes snapshot needs to be updated and commited as well. But do not worry just open a PR with what you have. If something is missing I can then always comment there. |
Discussed in #966
Originally posted by mattis-rosenkranz July 29, 2021
The generated OpenaAPI-Scheme component attributes are not inflected using the settings described in the docs.
This is not a problem as the parser just leaves the attribute names as they are, but it would be nice to conform the OpenAPI-scheme to the chosen field format.
Most likely this will be fixed in map_serialzer function.
The text was updated successfully, but these errors were encountered: