fix(models): enable 'populate_by_name' to alias fields correctly #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds
"populate_by_name": True
to themodel_config
for theSecurityScheme
modelContext
When creating the application, we can define supported security schemes using plain dicts or the
SecurityScheme
object. TheSecurityScheme
object is more typesafe but must eventually be dumped to JSON in order for the API docs to be generated.OR
The
in
keyword is reserved in Python which is why it is currently aliased tosecurity_scheme_in
however themodel_dump
invocation doesn't actually alias it correctly unlesspopulate_by_name
is enabled.Checklist:
pytest tests
and no failed.ruff check flask_openapi3 tests examples
and no failed.mypy flask_openapi3
and no failed.mkdocs serve
and no failed.