You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As seen from this answer, marshmallow supports usage of schema instance as nested field of outer schema.
Question in that StackOverflow thread contains one of the examples, when this could be useful and exact use-case we have in our project.
Unfortunately, flask_accepts doesn't support such behaviour at the moment. Usage of schema instance results in Error, thrown in flask_accepts/utils.py at this line of code:
I could submit a fix for that by the end of today. The only change added will be this one:
Note: In the future this could be improved to iteration over type_map keys and ensuring isinstance for all of them.
This would make available usage of marshmallow feature to extend existing marshmallow fields
The text was updated successfully, but these errors were encountered:
As seen from this answer, marshmallow supports usage of schema instance as nested field of outer schema.
Question in that StackOverflow thread contains one of the examples, when this could be useful and exact use-case we have in our project.
Unfortunately, flask_accepts doesn't support such behaviour at the moment. Usage of schema instance results in Error, thrown in flask_accepts/utils.py at this line of code:
I could submit a fix for that by the end of today. The only change added will be this one:
Note: In the future this could be improved to iteration over type_map keys and ensuring isinstance for all of them.
This would make available usage of marshmallow feature to extend existing marshmallow fields
The text was updated successfully, but these errors were encountered: