Anders
Anders
I'm guessing it was implemented like that because the developer(s) wanted the diff to include potential changes in other fields on [the M2M `through` model](https://docs.djangoproject.com/en/stable/ref/models/fields/#django.db.models.ManyToManyField.through) 🤔 However, tracking changes in...
Would you mind providing a minimal example? 🙂 I'm not able to reproduce the error on either version 3.1.1 nor 3.3.0 (nor the current `master` branch), using the following code...
@lazarust When you're mentioning "You can currently set a table name for the main table", I'm assuming you're talking about [the `table_name` parameter](https://django-simple-history.readthedocs.io/en/latest/historical_model.html#custom-history-table-name)..? In that case, what @antoineauger is talking...
Btw, if you (or anyone reading this) would like to add type hints to this project's code, feel free to open a PR! 😊 (Keep in mind that we currently...
I'm fairly sure this is a bug with the same cause as #1063 - which seems to be that [each history record's `instance` property](https://github.com/jazzband/django-simple-history/blob/aa87e7c85fbdcb51ea1f6e8dbde260c2d23c8430/simple_history/models.py#L490-L515) doesn't provide any related managers for...
I'm not sure I understand exactly how I would translate your description to code able to reproduce the warning/error, so would you mind providing a more complete, but still minimal,...
Sure, thank you for the PR! 😊 I'm not sure this is the best way of solving the issue, as how would a user know that the value `None` means...
[Duplicates #521 and #533] Thank you for reporting this! I'm planning on changing the implementation of the historical models' `__str__()` so that it returns a more generic string if a...
@raunaq-sailo Just as a heads-up, I'm considering implementing the changes I suggested myself, if no activity has happened within a couple weeks :)