We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Dictionary (schemaless) field is first most needed field for jsonmodels:
And there are good reasons to having one - for example we could have a list of tags like {"tag1": "value1", "tag2": 123, ..., "tagn": None}.
{"tag1": "value1", "tag2": 123, ..., "tagn": None}
(This is part of bigger problem -> #143)
The question is how to implement it - we can choose either of those two pull requests as base, or came up with something different.
Things to consider:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Dictionary (schemaless) field is first most needed field for jsonmodels:
And there are good reasons to having one - for example we could have a list of tags like
{"tag1": "value1", "tag2": 123, ..., "tagn": None}
.(This is part of bigger problem -> #143)
The question is how to implement it - we can choose either of those two pull requests as base, or came up with something different.
Things to consider:
The text was updated successfully, but these errors were encountered: