-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have option to use django-cleanup explicitly on models #75
Comments
Maybe extends from some class instead? class UserImage(cleanup.CleanUp, models.Model):
image = models.FileField() |
My initial thought is that the implementation would follow the way that Then add additional configuration in addition to the default
Not sure about the extends method, it would seem to bring in defining how it works with inheritance. Right now |
@vinnyrose that sounds like a fine solution. FWIW, our project decided to use django-cleanup as it is and add Thank you for this project by the way. It's super useful. |
Greetings ! sorry for SPAM message. but i would say thanks to django-cleanup developers ;X Tnx a lot for this module :XXXXX |
@vinnyrose That solution sounds great, and I would still love to see it implemented, if it is still in the works. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
By default, django-cleanup works by cleaning all models unless you explicitly ignore them with
@cleanup.ignore
. I'm wondering if django-cleanup could work in such a way that it doesn't cleanup any models unless you explicitly ask it to?For example:
The text was updated successfully, but these errors were encountered: