From 0d3c3b1197272f7d25f456a059d930dfb84828d1 Mon Sep 17 00:00:00 2001 From: Michal Sniatala Date: Wed, 4 Dec 2024 07:44:14 +0100 Subject: [PATCH] docs: update note about required filters (#9298) * docs: update note about required filters * Update user_guide_src/source/incoming/filters.rst Co-authored-by: John Paul E. Balandan, CPA --------- Co-authored-by: John Paul E. Balandan, CPA --- user_guide_src/source/incoming/filters.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user_guide_src/source/incoming/filters.rst b/user_guide_src/source/incoming/filters.rst index 737fd191392a..14b110e34a12 100644 --- a/user_guide_src/source/incoming/filters.rst +++ b/user_guide_src/source/incoming/filters.rst @@ -132,7 +132,7 @@ They are special filters that are applied to every request made by the framework. They are applied before and after other kinds of filters that are explained below. -.. note:: The Required Filters are always executed even if a route does not exist. +.. note:: The Required Filters are always executed. However, if the route does not exist, only the Before Filters are executed. You should take care with how many you use here, since it could have performance implications to have too many run on every request. But the filters set by default