Anders
Anders
> I think this is fine, but I would like to raise a slight change in implementation. Rather than always showing the change at the end, would it make more...
@tim-schilling I realized some additional changes needed to be made to properly display foreign keys and M2M objects, and so most of the recent commits were made to facilitate that...
@tim-schilling I mainly added some (presumably final) polish commits - including fd72e7a5f9943a3d93be4066a97ed6d946b0c4d8 and 38ec0c2049bc2388408d0701a69cefed1bbad45d, which improve how really long strings are displayed - and added tests for how safe strings...
> Not having code coverage hurts us here because that would confirm that the code is actually running in the tests. True.. From [the workflow logs](https://github.com/jazzband/django-simple-history/actions/runs/8939661574/job/24556138070?pr=1128) (under "Upload coverage"), it...
Finished cleaning up the commits, so the PR is ready for merging :) *([A few minor changes done while rebasing](https://github.com/jazzband/django-simple-history/compare/5a772dd71c37311ba3b5d08abc6d8a24e93016d2..733f4e0a6046917848ef46277079cefcf6c87c98))*
@jurrian Sorry for the (very) late reply; I'm busy with some of the other PRs, currently, but this is definitely on my TODO list 🙂
Can I ask what these `TranslationCharField` and `TranslationTextField` classes are? Nothing relevant comes up when I [google them](https://www.google.com/search?q=django+%22TranslationCharField%22+OR+%22TranslationTextField%22), and so it seems like they're part of some of your project's...
Closing due to stale issue; see https://github.com/jazzband/django-simple-history/issues/1299#issuecomment-2096951303
Sure, as long as removing it doesn't severely affect performance in some cases (which I assumed was the reason it was added in the first place, but perhaps not..?), I'm...
> @jeking3 I believe you added this method in https://github.com/jazzband/django-simple-history/pull/866. I'd love to get your opinion on this. Btw, it looks like the method was mainly added by @TyrantWave in...