Moving images from provider docs to providers/ subdir

This commit is contained in:
Roman Mogilatov 2015-07-25 00:51:14 +03:00
parent 947a0667a6
commit 244e2bcfb9
14 changed files with 10 additions and 10 deletions

View File

Before

Width:  |  Height:  |  Size: 38 KiB

After

Width:  |  Height:  |  Size: 38 KiB

View File

Before

Width:  |  Height:  |  Size: 41 KiB

After

Width:  |  Height:  |  Size: 41 KiB

View File

Before

Width:  |  Height:  |  Size: 7.6 KiB

After

Width:  |  Height:  |  Size: 7.6 KiB

View File

Before

Width:  |  Height:  |  Size: 32 KiB

After

Width:  |  Height:  |  Size: 32 KiB

View File

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 21 KiB

View File

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 18 KiB

View File

Before

Width:  |  Height:  |  Size: 33 KiB

After

Width:  |  Height:  |  Size: 33 KiB

View File

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 34 KiB

View File

Before

Width:  |  Height:  |  Size: 9.7 KiB

After

Width:  |  Height:  |  Size: 9.7 KiB

View File

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

View File

@ -15,7 +15,7 @@ Context keyword arguments have higher priority than ``KwArg`` injections.
Example:
.. image:: /images/callable.png
.. image:: /images/providers/callable.png
:width: 100%
:align: center

View File

@ -35,7 +35,7 @@ Example:
Instead of this, ``UserService`` has external dependency, that has to
be satisfied by cleint's code, out of library's scope.
.. image:: /images/external_dependency.png
.. image:: /images/providers/external_dependency.png
.. code-block:: python

View File

@ -5,7 +5,7 @@ Factory providers
Nothing could be better than brief example:
.. image:: /images/factory.png
.. image:: /images/providers/factory.png
:width: 80%
:align: center
@ -69,7 +69,7 @@ Example below shows how to create ``Factory`` of particular class with
``__init__`` keyword argument injections which injectable values are also
provided by another factories:
.. image:: /images/factory_init_injections.png
.. image:: /images/providers/factory_init_injections.png
.. code-block:: python
@ -120,7 +120,7 @@ useful for testing).
So, please, follow the example below:
.. image:: /images/factory_init_injections_and_contexts.png
.. image:: /images/providers/factory_init_injections_and_contexts.png
.. code-block:: python
@ -208,7 +208,7 @@ with injectable values right after object's creation.
Example:
.. image:: /images/factory_attribute_injections.png
.. image:: /images/providers/factory_attribute_injections.png
.. code-block:: python
@ -280,7 +280,7 @@ some cases.
Example:
.. image:: /images/factory_method_injections.png
.. image:: /images/providers/factory_method_injections.png
.. code-block:: python
@ -364,7 +364,7 @@ factory.
Example:
.. image:: /images/factory_delegation.png
.. image:: /images/providers/factory_delegation.png
.. code-block:: python

View File

@ -6,7 +6,7 @@ and returns same instance on every next call.
Example:
.. image:: /images/singleton.png
.. image:: /images/providers/singleton.png
:width: 80%
:align: center
@ -41,7 +41,7 @@ Singleton providers and injections
specified class instance, so, all of the rules about injections are the same,
as for ``Factory`` providers.
.. image:: /images/singleton_internals.png
.. image:: /images/providers/singleton_internals.png
:width: 80%
:align: center