fix hardcoded AUTH_USER_MODEL in migrations #677
Closed
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
|
It seems like this may be a duplicate of #572 .. but any way one of these can be merged in and released? 😄 |
|
closing in favour of #572 |
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.
Hi there 👋
Great project! I wanted to contribute to fixing a "bug" I realized in the migrations. When you set
USER_MODELas such in yoursettings.py:the migrations still create a foreign key reference to the value of
AUTH_USER_MODEL.This PR would update that to use the value of
settings.PUSH_NOTIFICATION_SETTINGS["USER_MODEL"]