IMO the CurrentUserField should not have on_delete=CASCADE as a default parameter. Instead it should align with Django (3.2) ForeignKey field implementation, where the parameter for on_delete is required.
The current behaviour might lead to unwanted deletion if the user is deleted.
IMO the CurrentUserField should not have
on_delete=CASCADE
as a default parameter. Instead it should align with Django (3.2) ForeignKey field implementation, where the parameter foron_delete
is required.The current behaviour might lead to unwanted deletion if the user is deleted.
Thank you for considering my request.