You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subclasses should be allowed to declare usage of a given many_many through join class. For example, say I have a module that provides a MySpecialModel class. I want to make it easy to have a many_many through relation from this class to pages - but explicitly to pages. My use case doesn't allow random dataobjects to own my special model.
The below code demonstrates how this could be used (replacing MySpecialModel with Image so you can dump this int a project and try it out).
This fails because the linking object's relation class doesn't exactly match the owner. Sharing the linking objects across various entries in the ancestry should be a supported use case.
@emteknetnz You've assigned this to me but the PR is merged - before I close this I just want to double check if that was a mistake, or if there's something I'm missing here?
Subclasses should be allowed to declare usage of a given many_many through join class. For example, say I have a module that provides a
MySpecialModel
class. I want to make it easy to have a many_many through relation from this class to pages - but explicitly to pages. My use case doesn't allow random dataobjects to own my special model.The below code demonstrates how this could be used (replacing
MySpecialModel
withImage
so you can dump this int a project and try it out).This fails because the linking object's relation class doesn't exactly match the owner. Sharing the linking objects across various entries in the ancestry should be a supported use case.
PRs
The text was updated successfully, but these errors were encountered: