From 71e9694856627d4027c9df066045f0e1c2b5cf27 Mon Sep 17 00:00:00 2001
From: Joseph Victor Zammit <jvzammit@gmail.com>
Date: Sat, 22 Oct 2022 18:52:53 +0200
Subject: Fixed #30801 -- Improved guidance for making good use of signals.

---
 docs/ref/signals.txt | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

(limited to 'docs/ref')

diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index d9c07b415c..0e2a701fcd 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -22,6 +22,14 @@ Model signals
 The :mod:`django.db.models.signals` module defines a set of signals sent by the
 model system.
 
+.. warning::
+
+    Signals can make your code harder to maintain. Consider implementing a
+    helper method on a :ref:`custom manager <custom-managers>`, to
+    both update your models and perform additional logic, or else
+    :ref:`overriding model methods <overriding-model-methods>` before using
+    model signals.
+
 .. warning::
 
     Many of these signals are sent by various model methods like
@@ -546,6 +554,12 @@ Request/response signals
 
 Signals sent by the core framework when processing a request.
 
+.. warning::
+
+    Signals can make your code harder to maintain. Consider :doc:`using a
+    middleware </topics/http/middleware>` before using request/response
+    signals.
+
 ``request_started``
 -------------------
 
-- 
cgit v1.3