mirror of
https://github.com/ets-labs/python-dependency-injector.git
synced 2025-07-09 15:42:23 +03:00
Fix some wording
This commit is contained in:
parent
647f76a78a
commit
cb9686fc59
|
@ -124,7 +124,7 @@ Put next into the ``views.py``:
|
||||||
|
|
||||||
Ok, we have the view.
|
Ok, we have the view.
|
||||||
|
|
||||||
Now let's create the heart of our application - the container. Container will keep all of the
|
Now let's create the main part of our application - the container. Container will keep all of the
|
||||||
application components and their dependencies. First two providers we need to add are
|
application components and their dependencies. First two providers we need to add are
|
||||||
the ``Flask`` application provider and the view provider.
|
the ``Flask`` application provider and the view provider.
|
||||||
|
|
||||||
|
@ -150,8 +150,8 @@ Put next into the ``containers.py``:
|
||||||
|
|
||||||
Finally we need to create the Flask application factory. It is traditionally called
|
Finally we need to create the Flask application factory. It is traditionally called
|
||||||
``create_app()``. It will create the container. Then it will use the container to create
|
``create_app()``. It will create the container. Then it will use the container to create
|
||||||
the Flask application. Last step is to configure the routing - we will assign ``index_view`` from the
|
the Flask application. Last step is to configure the routing - we will assign ``index_view`` from
|
||||||
container to handle user requests to the root ``/`` if our web application.
|
the container to handle user requests to the root ``/`` of our web application.
|
||||||
|
|
||||||
Put next into the ``application.py``:
|
Put next into the ``application.py``:
|
||||||
|
|
||||||
|
@ -1087,8 +1087,8 @@ We are done.
|
||||||
It this tutorial we've build ``Flask`` application following dependency injection principle.
|
It this tutorial we've build ``Flask`` application following dependency injection principle.
|
||||||
We've used ``Dependency Injector`` as a dependency injection framework.
|
We've used ``Dependency Injector`` as a dependency injection framework.
|
||||||
|
|
||||||
The heart of this application is the container. It keeps all the application components and their
|
The main part of this application is the container. It keeps all the application components and
|
||||||
dependencies in one place:
|
their dependencies in one place:
|
||||||
|
|
||||||
.. code-block:: python
|
.. code-block:: python
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user