Ignore null changeset on creation and deletion

[joeyjoejoejr]

Problem

I registered a nullable field of a model using include_fields. There was a a check for null changes in the log_update receiver, but not the log_create and log_delete ones. This meant that a log entry was created with null for the changes field whenever a model was created or updated, but didn't have a value for that field.

When the mixin method msg_short is called in the Audit Log admin index, it would error because it's expecting an object for changes.

What Changed:

• Made the SimpleIncludeModel label field nullable
• Added tests for creation and deletion of a model with a null label field
• Added checks to log_create and log_delete to make sure entries aren't created if the changes are None.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.02%. Comparing base (31418d5) to head (3aaada0).
Report is 242 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #282      +/-   ##
==========================================
- Coverage   82.20%   82.02%   -0.19%     
==========================================
  Files          18       18              
  Lines         489      495       +6     
==========================================
+ Hits          402      406       +4     
- Misses         87       89       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hramezani]

Thanks @joeyjoejoejr for the patch 👍
Could you please rebase your patch?

[aqeelat]

@hramezani I think will be solved as a side-effect of #483. We might still need the tests but let's evaluate after we merge #483.