Use Django 3.1 models.JSONField #33
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
This drops all prior Django support and will take us to v5 for this library. As such, migrations have been reset to a single initial migration which should be fine if upgrading prior versions as there has been no schema change but should alleviate having to have postgres installed just to run migrations.
From #22 Copying in rather than dealing with merge because of the JSONField and migrations changes
Codecov Report
@@ Coverage Diff @@
## master #33 +/- ##
===========================================
+ Coverage 80.20% 92.75% +12.54%
===========================================
Files 6 5 -1
Lines 96 69 -27
Branches 10 5 -5
===========================================
- Hits 77 64 -13
+ Misses 14 4 -10
+ Partials 5 1 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
This drops all prior Django support and will take us to v5 for this library. As such, migrations have been reset to a single initial migration which should be fine if upgrading prior versions as there has been no schema change but should alleviate having to have postgres installed just to run migrations.