Allow nullable/blank fields, fix header values #58
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
anx-ckreuzberger
force-pushed
the
nullable-fields
branch
from
df8e677
to
f62b666
Compare
anx-ckreuzberger
force-pushed
the
nullable-fields
branch
from
f62b666
to
9c64ea6
Compare
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.
Based on the discussion in #34 as well as the comment of @vonorm in #40, this PR properly uses
DJANGO_REST_PASSWORDRESET_HTTP_USER_AGENT_HEADERandDJANGO_REST_PASSWORDRESET_IP_ADDRESS_HEADER.It also enables empty/nullable values for user agent and remote address.