Added protect namespace to Pydantic v2 ConfigDict #1489
Merged
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.
In Pydantic v2, a new "feature" was introduced that warned you if your field keys began with
model_
. However we have several fields that need to be named as such. So per Pydantic docs, this warning can be removed by settingprotected_namespaces = ()
to remove the default protected namespacemodel_
.This PR allows an
extra_data_template
JSON file such as the following to be passed into the datamodel-codgen tool and have theprotected_namespace
change actually take affect. I verified that the warnings disappear on my project after this change.