fix: Added related_name to version content type field #274
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.
Description
This adds the
related_name
attribute to thecontent_type
field of theVersion
model.Currently the reverse lookup from a queryset will be using django's default name of
version_set
. That default is the reason for this change. By having this app installed, an application cannot have another model calledVersion
with aForeignKey
toContentType
.This is a breaking change if an application is making queries which access that reverse relationship. Currently they'd be doing something like;
This would need to become the following with this change;
Related resources
Checklist
master
Slack to find a “pr review buddy” who is going to review my pull request.