ignore_duplicate fields

[TonisPiip]

from https://github.com/etianen/django-reversion/issues/957

And also in the linked issue above, it was said it's a bad idea to exclude fields, but I wonder, where is that mentioned in the docs, or is there some best practices? Or is there some way to exclude fields, so they are still tracked, but not have the fields be considered when it's checking the logic for ignore_duplicates?

---

implementation idea:

either:

• ignore_duplicates allows also being an itterable list of field names, which are ignored when checking if it's a duplicate revision. (As it's also bool() true. and if you set the list of fields, it makes sense you're also ignoring duplicates)
• explicit new field

[etianen]

ignore_duplicates allows also being an itterable list of field names ☝️ This sounds nice!