-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Schemaless fields #143
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need schemaless fields that can handle non-strict json data - lets imagine we are trying to handle 3rd party api that was not designed with jsonmodels first - such api may behave in a way that cannot be handled with models - for example json object with variant names (like list of tags) or list that can contain both scalars and objects (and lists and anything you can write with json).
Although we should keep the mindset 'jsonmodels first can make you data sane' - we should be able to handle more generic cases.
There are some questions for this:
null
- should we even handle such cases?The text was updated successfully, but these errors were encountered: