Fix Validator::complete not being implemented properly for all validator types #494
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.
This resolves the issue of some definitions refs not getting updated properly.
The issue in pydantic only required the fix for ModelValidator, but the comments where this stuff is used seemed to indicate that every contained validator should have
complete
called. So I went through all the files and made sure this was done (many were missing this).I think it might be preferable if you had to explicitly define the
fn complete
for each Validator type and didn't get a default for free, but I don't know how hard that would be to refactor. (Yes there would be a bunch of trivial implementations but I feel that's less likely to cause errors than forgetting to "complete" a new validator type.)Alternatively I guess it could make sense to refactor so this "completion" wasn't necessary, if that's even possible, but I also don't know how hard that would be.