Add converter for django 3.1 JSONField #1017
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nikolaik
force-pushed
the
fix/django-3.1-jsonfield
branch
from
1ba2db2
to
25de313
Compare
|
Thanks @nikolaik . Django v3.1 has been released now so could you add it to the test matrix? |
yaz, done |
jkimbo
approved these changes
Aug 7, 2020
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should probably wait until django 3.1 is released and possible to add to the test matrix.
Also found #303 thread suggesting people have a use case for converting JSONField (django 3.1, django_mysql and postgres ones) to
GenericScalar. I'm not sure what is most common.