Remove has_related_links option from models
Reported by: |
Adrian Holovaty |
Owned by: |
Adrian Holovaty |
Component:
|
Metasystem
|
Version:
|
|
Severity:
|
minor
|
Keywords:
|
|
Cc:
|
|
Triage Stage:
|
Unreviewed
|
Has patch:
|
no
|
Needs documentation:
|
no
|
Needs tests:
|
no
|
Patch needs improvement:
|
no
|
Easy pickings:
|
no
|
UI/UX:
|
no
|
Pull Requests: | 19109 build:success, 18929 merged, 19112 merged, 18140 merged, 18085 unmerged, 18065 merged, 17313 merged, 17129 merged, 17218 merged, 17027 merged, 16639 merged, 16498 merged, 16409 merged, 16382 merged, 16011 unmerged, 14798 merged, 7653 merged, 14605 merged, 14603 merged, 13192 merged, 14123 merged, 14050 merged, 13915 merged, 13894 merged, 12932 merged, 12929 merged, 12575 merged, 11962, 11495, 7756 |
---|
|
The current (undocumented) has_related_links
code is too Ellington-specific and doesn't belong in Django. Let's remove it.
We'll have to come up with a more generic way of associating content_type_id/object_id relationships, such as related links, to a model.
Resolution: |
→ fixed
|
Status: |
new → closed
|
Fixed in magic-removal a while ago.