Added related_name to both OutstandingToken as well as BlacklistedToken #720
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
|
@Andrew-Chen-Wang Ready for review. |
|
this is a breaking change. also requires a new migration breaking change will need to wait for new major version |
|
@Andrew-Chen-Wang do I need to make those migrations? Or is that something that happens throughout the release of a new major version? |
|
need new migration |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Not a huge change, but this would make the reverse relation reference easier from both the user perspective as well as the OutstandingToken perspective:
user.outstandingtoken_setbecomesuser.outstanding_tokensThe same for the BlacklistedToken