Change Types

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

I was always frustrated when I got error mails because of changes in volatile model attributes (e.g. League name). In these cases I had to manually find out the changes and update those entities in the backend. With the improvements in this Pull Request the volatile (non-identity-relevant) attributes will automatically be updated on the respective management commands (setup, import_games, import_report)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read CONTRIBUTING.md.
[x] I have added tests to cover my changes.
[x] My tests run automatically.
[x] All new and existing tests passed.

djbrown / hbscorez

Update volatile model metadata in import commands #125

Change Types

Description

Checklist