-
-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot resolve a custom through model passed as app_label.ModelName for m2m relations #1266
Comments
/cc @ddabble |
This is still a problem despite the fixes brought by release |
Yeah, this wasn't addressed in 3.5.0, but it's on my personal TODO list - provided that no one fixes it before I get to it 🙂 |
any updates on this? |
I have a proposed fix for this here: #1390. Feedback and any additional testing are welcome. |
…ings jazzband#1266 resolving through tables defined as strings on m2m relations
+1, not working with |
Would love to see this get merged! This was blocking us from having history working reliably on some of our models. |
m2m_fields is working with through if your model class is defined like this i.e. non string format:
|
PS: this is a corner case of #1093. I made some experiments in #1149 before creating this issue because I don't have the required knowledge to fix it.
Describe the bug
django-simple-history cannot resolve a custom through model passed as
app_label.ModelName
for m2m relations.To Reproduce
When trying to pass the
Membership
model as atests.Membership
string, this produces an error when testing inside the project repository withpython3 runtests.py
:Test output:
Expected behavior
It correctly works when passing the
Membership
model as a Python class:Environment (please complete the following information):
3.4.0
4.2.5
The text was updated successfully, but these errors were encountered: