GIT-37: fix blueprint middleware application (#1690)
* GIT-37: fix blueprint middleware application 1. If you register a middleware via `@blueprint.middleware` then it will apply only to the routes defined by the blueprint. 2. If you register a middleware via `@blueprint_group.middleware` then it will apply to all blueprint based routes that are part of the group. 3. If you define a middleware via `@app.middleware` then it will be applied on all available routes Fixes #37 Signed-off-by: Harsha Narayana <harsha2k4@gmail.com> * GIT-37: add changelog Signed-off-by: Harsha Narayana <harsha2k4@gmail.com>
This commit is contained in:
committed by
Stephen Sadowski
parent
179a07942e
commit
a6077a1790
11
changelogs/37.bugfix.rst
Normal file
11
changelogs/37.bugfix.rst
Normal file
@@ -0,0 +1,11 @@
|
||||
Fix blueprint middleware application
|
||||
|
||||
Currently, any blueprint middleware registered, irrespective of which blueprint was used to do so, was
|
||||
being applied to all of the routes created by the :code:`@app` and :code:`@blueprint` alike.
|
||||
|
||||
As part of this change, the blueprint based middleware application is enforced based on where they are
|
||||
registered.
|
||||
|
||||
- If you register a middleware via :code:`@blueprint.middleware` then it will apply only to the routes defined by the blueprint.
|
||||
- If you register a middleware via :code:`@blueprint_group.middleware` then it will apply to all blueprint based routes that are part of the group.
|
||||
- If you define a middleware via :code:`@app.middleware` then it will be applied on all available routes
|
||||
Reference in New Issue
Block a user