forked from orbit-oss/flask
Docs typo/markup fixes (#5829)
This commit is contained in:
parent
adf363679d
commit
88a65bb374
2 changed files with 5 additions and 5 deletions
|
|
@ -141,8 +141,8 @@ real object, rather than the proxy. Use the
|
|||
my_signal.send(app)
|
||||
|
||||
|
||||
Lifcycle of the Context
|
||||
-----------------------
|
||||
Lifecycle of the Context
|
||||
------------------------
|
||||
|
||||
Flask dispatches a request in multiple stages which can affect the request,
|
||||
response, and how errors are handled. See :doc:`/lifecycle` for a list of all
|
||||
|
|
|
|||
|
|
@ -178,10 +178,10 @@ etc. Context locals are specific to the worker handling the activity, such as a
|
|||
thread, process, coroutine, or greenlet.
|
||||
|
||||
The context and proxies help solve two development issues: circular imports, and
|
||||
passing around global data. :data:`.current_app: can be used to access the
|
||||
passing around global data. :data:`.current_app` can be used to access the
|
||||
application object without needing to import the app object directly, avoiding
|
||||
circular import issues. :data:`.request`, :data:`.session`, and :data`.g` can be
|
||||
imported to access the current data for the request, rather than needing to
|
||||
circular import issues. :data:`.request`, :data:`.session`, and :data:`.g` can
|
||||
be imported to access the current data for the request, rather than needing to
|
||||
pass them as arguments through every single function in your project.
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue