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.
I found current wrappers concept a bit confusing and problematic to follow.
Instead of trying to copy validator class and add vaa api over it, I suggest to completely split them from each other.
So example from doc:
Will look like this:
Also now validation is triggered on init of the validator (so cleaned_data or errors could be accessed right away)
It keeps follow current api (none of tests were changed and all works just fine).
But if there any reasons to be triggered only by is_valid method, I can change it later
Also support for pydantic added