forked from orbit-oss/flask
Fix various small spelling errors.
This commit is contained in:
parent
7f782ba84e
commit
4e272fc042
9 changed files with 14 additions and 14 deletions
|
|
@ -244,7 +244,7 @@ was dispatched to any other admin blueprint endpoint.
|
|||
Error Handlers
|
||||
--------------
|
||||
|
||||
Blueprints support the errorhandler decorator just like the :class:`Flask`
|
||||
Blueprints support the ``errorhandler`` decorator just like the :class:`Flask`
|
||||
application object, so it is easy to make Blueprint-specific custom error
|
||||
pages.
|
||||
|
||||
|
|
@ -259,7 +259,7 @@ concerning handlers for 404 and 405 exceptions. These errorhandlers are only
|
|||
invoked from an appropriate ``raise`` statement or a call to ``abort`` in another
|
||||
of the blueprint's view functions; they are not invoked by, e.g., an invalid URL
|
||||
access. This is because the blueprint does not "own" a certain URL space, so
|
||||
the application instance has no way of knowing which blueprint errorhandler it
|
||||
the application instance has no way of knowing which blueprint error handler it
|
||||
should run if given an invalid URL. If you would like to execute different
|
||||
handling strategies for these errors based on URL prefixes, they may be defined
|
||||
at the application level using the ``request`` proxy object::
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue