fix(api-model): correct AllOptionalMetaclass
for field validation in form models
#1924
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.
The goal of this PR is to correct the implementation of the
AllOptionalMetaclass
metaclass used to implement Pydantic models for reading and updating configuration data (short-term storage, thermal clusters, renewable resources clusters, etc.).The metaclass has been fixed to allow field validation when they come from an ancestor class to the model (using inheritance).
The
use_none
option has been added to the metaclass parameters to indicate that we want to use theNone
value instead of the default values. This is necessary, for example, to update certain fields of a model while leaving other fields unchanged: theNone
value is used to indicate the fields that we wants to preserve.Unit tests have been corrected to take into consideration the form field validation (previously, validation was not occurring).
Minor changes have been made to correct the documentation and reorganize/fix module imports.