Marshmallow 3.10.0 warning on using explicit `metadata=...`
See original GitHub issueWhen using marshmallow version 3.10.0 this warning appears:
RemovedInMarshmallow4Warning: Passing field metadata as a keyword arg is deprecated.
Use the explicit `metadata=...` argument instead.
Here is the commit where they have changed the behavior. https://github.com/marshmallow-code/marshmallow/commit/013abfd669f64446cc7954d0320cf5f1d668bd49
I understand this is something that needs to be addressed on the marshmallow_dataclass
side, right?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Changelog — marshmallow 3.19.0 documentation
Passing field metadata via keyword arguments is deprecated and will be removed in marshmallow 4 (#1350). Use the explicit metadata=... argument instead.
Read more >marshmallow NewType can not be turned into a dataclass ...
To avoid this message, make sure all your classes and all the classes of their fields are either explicitly supported by marshmallow_dataclass, ...
Read more >upgrade-marshmallow - Python Package Health Analysis - Snyk
Upgrade marshmallow is a tool to batch modify call expression with "marshmallow.fields.Field". For more information about how to use this ...
Read more >marshmallow_dataclass 0.1.0 documentation - Ophir LOJKINE
It takes a python class, and generates a marshmallow schema for it. ... or define the schema explicitly using " "field(metadata=dict(marshmallow_field=.
Read more >apispec - Read the Docs
from apispec.ext.marshmallow import MarshmallowPlugin ... Stores metadata that describes a RESTful API using the OpenAPI specification.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, I think the only thing we can do here is follow marshmallow and update our documentation to ask people to use an explicit
metadata
key. PR welcome for the docs and readme changes.Same for
exclude
field here