handle default issue with multiple inheritance #687
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.
This is something we can handle in our implementation but, we wanted to put this up in case it would be helpful to others.
Prior to the pydantic 2.0 change, we were able to define abstract classes as
RedisModel's and then, in implementation we could define whether we wanted it to be aHashModelor aJsonModel. After the change, any defaults we had were coming through asExpressionProxyobjects for the models with the mixins.This fix handles multiple bases on a model to prevent this from happening.