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.

Sign up for GitHub

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

Jump to bottom

Dictionary field #145

Open

beregond opened this issue Feb 28, 2021 · 0 comments

Projects

Collaborator

beregond commented Feb 28, 2021 •

edited

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:

how deep the constraints should go? We can either declare 'object', or some valid types, or even TypedDict?

The text was updated successfully, but these errors were encountered:

beregond created this issue from a note in development (Limbo)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment