Update UniqueFieldsMixin to support DRF 3.11 validator context API #96
Conversation
This file contains hidden or 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
Codecov Report
@@ Coverage Diff @@
## master #96 +/- ##
==========================================
- Coverage 99.05% 98.59% -0.47%
==========================================
Files 3 3
Lines 211 213 +2
==========================================
+ Hits 209 210 +1
- Misses 2 3 +1
Continue to review full report at Codecov.
|
|
@mands Thanks, merged |
|
Available on PyPI as v0.5.4 |
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.
DRF 3.11 changed how context is passed into validators to fix a race-condition, as described in the following links
set_context()encode/django-rest-framework#7062This PR provides support for this new API in a backwards-compatible way, using
set_contextif available/on older DRF, and passing the field in with the__call__if not.