Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Field not properly supported in deserialization? #41

Open
puma314 opened this issue Jul 12, 2021 · 1 comment
Open

Field not properly supported in deserialization? #41

puma314 opened this issue Jul 12, 2021 · 1 comment

Comments

@puma314
Copy link

puma314 commented Jul 12, 2021

I noticed that in deserialization, the code checks if the serialization is a Schema or a Field and serializes accordingly (slightly different logic for the 2 cases) (link here).

But during serialization, I noticed there isn't support for a field, which results in errors when using a Field instead of a Schema when defining the aggregate_result_serialization (link here).

@Bachmann1234
Copy link
Owner

So its been a while since I have done much on this library. So its possible something on marshmallow's side updated.

Do you have some example code that is not doing what you expect?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants