Changes between Initial Version and Version 1 of Ticket #34061


Ignore:
Timestamp:
Sep 28, 2022, 8:39:16 PM (2 years ago)
Author:
Aaron Smith
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34061 – Description

    initial v1  
    33Not running validations by default is a **serious** footgun that has ruined more than one developer's day. Yes, it's in the documentation. But the broad expectation is that a web framework will do this sort of thing by default without extra configuration or overrides. Model validations should function as expected ''by the naive'' regardless of how the model is saved.
    44
    5 Ideally the Model class should call `full_clean()` in it's save method. If this can't be done for backwards compatibility (which is a silly reason, but I digress) I propose we add a new `ValidatedModel` class that subclasses `Model`. There should be a clear and obvious option to fulfill the basic and reasonable expectations of the new Django developer.
     5Ideally the Model class should call `full_clean()` in it's save method. If this can't be done for backwards compatibility, I propose we add a new `ValidatedModel` class that subclasses `Model`. There should be a clear and obvious option to fulfill the basic and reasonable expectations of the new Django developer.
    66
    77I'm more than happy to make this PR.
Back to Top