diff options
| author | Carlton Gibson <carlton.gibson@noumenal.es> | 2021-11-04 15:12:08 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-11-05 09:22:53 +0100 |
| commit | 2c01ebb4be5d53cbf6450f356c10e436025d6d07 (patch) | |
| tree | 840780e8970b738593ac963e299a98274ce73551 | |
| parent | 4816dc942860caf076c7c85ea9dbfa8bfab212ff (diff) | |
Refs #33263 -- Expanded release notes for DeleteView adopting FormMixin.
| -rw-r--r-- | docs/releases/4.0.txt | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/releases/4.0.txt b/docs/releases/4.0.txt index 9089117215..7e6c4f62cc 100644 --- a/docs/releases/4.0.txt +++ b/docs/releases/4.0.txt @@ -273,6 +273,10 @@ Generic Views deletion. In addition, this allows ``DeleteView`` to function with :class:`django.contrib.messages.views.SuccessMessageMixin`. + In accordance with ``FormMixin``, object deletion for POST requests is + handled in ``form_valid()``. Custom delete logic in ``delete()`` handlers + should be moved to ``form_valid()``, or a shared helper method, as needed. + Logging ~~~~~~~ @@ -477,6 +481,14 @@ As a side-effect, running ``makemigrations`` might generate no-op ``AlterField`` operations for ``ManyToManyField`` and ``ForeignKey`` fields in some cases. +``DeleteView`` changes +---------------------- + +:class:`~django.views.generic.edit.DeleteView` now uses +:class:`~django.views.generic.edit.FormMixin` to handle POST requests. As a +consequence, any custom deletion logic in ``delete()`` handlers should be +moved to ``form_valid()``, or a shared helper method, if required. + Miscellaneous ------------- |