-
Notifications
You must be signed in to change notification settings - Fork 71
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
Provide schema metadata in the "Meta" class #41
Comments
I think it does already :) |
Where, how? I'm quite surprised that this didn't get any reply. Looking at the code and tests, I can see there is a way to provide a field's metadata, but not the schema metadata. Any pointers? |
To add a bit more to the conversation, after checking the code and tests, here is the status for some metas:
Only remaining issue for me (after the next release), would be Would you accept to have a way to set it under the |
Hey @LukeMarlin thanks for digging in and pulling out some of those answers. Looking here it is setting |
Missed that! Given that 0.6 seems to date back to June 16, and that that line was added 22 days ago, that's probably the case. Is it possible to release a 0.7 in the near future? |
Just pushed 0.7.0. Hope that works for you! |
Thank you very much, trying that at work tomorrow :)
|
Works nicely on 0.7, thanks ! 🎉 Note: $id might be interesting for some users as well. |
- Refactor _resolve_additional_properties to reuse parts of it for title and description support - Add _get_schema_metadata that retrieves the 3 currently supported metadata options on a schema - Rename 'cls' params to something less confusing as 'cls' is a python keyword - Add documentation for title, description and additional_properties - Move addtional_properties tests to a new forlder "schema_metadata_tests" so they can be gathered in a common place Closes fuhrysteve#41
- Refactor _resolve_additional_properties to reuse parts of it for title and description support - Add _get_schema_metadata that retrieves the 3 currently supported metadata options on a schema - Rename 'cls' params to something less confusing as 'cls' is a python keyword - Add documentation for title, description and additional_properties - Move addtional_properties tests to a new forlder "schema_metadata_tests" so they can be gathered in a common place Closes fuhrysteve#41
- Refactor _resolve_additional_properties to reuse parts of it for title and description support - Add _get_schema_metadata that retrieves the 3 currently supported metadata options on a schema - Rename 'cls' params to something less confusing as 'cls' is a python keyword - Add documentation for title, description and additional_properties - Move addtional_properties tests to a new forlder "schema_metadata_tests" so they can be gathered in a common place Closes fuhrysteve#41
- Refactor _resolve_additional_properties to reuse parts of it for title and description support - Add _get_schema_metadata that retrieves the 3 currently supported metadata options on a schema - Rename 'cls' params to something less confusing as 'cls' is a python keyword - Add documentation for title, description and additional_properties - Move addtional_properties tests to a new forlder "schema_metadata_tests" so they can be gathered in a common place Closes fuhrysteve#41
Bump - please add 'title' and 'description' support. |
Marshmallow uses a nested
Meta
class in order to hold metadata about things like what fields to serialize. Can we use this schema to hold string fields abouttitle
,description
, and$schema
as defined in the JSON schema standard?The text was updated successfully, but these errors were encountered: