I’m trying to create a PR for the package django-cookie-consent and wondered what is the best way to do it:
The problem: the problem currently has a
LogItem model that saves an instance whenever a cookie is accepted or denied. This takes up space FAST, so I wanted to make it an optional model.
Solutions I can think of are:
Add a new setting and then check it whenever a cookie is saved or not. My question here is: does that means the user with
LogItemdisabled will still have an empty table created in their db? Or can I set the migration to be optional as well?
LogItemto an app of its own. Then the user must install it to
INSTALLED_APPSif they want it and each new log item would be created with… signals? … Is this a best practice, though?