Skip to content

Various fixes on the dependency injection component documentation. #1792

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 8, 2012
Merged

Various fixes on the dependency injection component documentation. #1792

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2900c25
fix minor typo
greg0ire Oct 7, 2012
f9ebd2c
added missing letter
greg0ire Oct 7, 2012
f99f223
Add missing apostrophe
greg0ire Oct 7, 2012
d3a157a
Try to fix a link
greg0ire Oct 7, 2012
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions components/dependency_injection/compilation.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ will then be called when the container is compiled::

.. note::

Compiler passes are registered differently is you are using the full
Compiler passes are registered differently if you are using the full
stack framework, see :doc:`/cookbook/service_container/compiler_passes`
for more details.

Expand Down Expand Up @@ -408,7 +408,7 @@ but getting an up to date configuration whilst developing your application::
This could be further improved by only recompiling the container in debug
mode when changes have been made to its configuration rather than on every
request. This can be done by caching the resource files used to configure
the container in the way describe in ":doc:`/components/config/caching`"
the container in the way described in ":doc:`/components/config/caching`"
in the config component documentation.

You do not need to work out which files to cache as the container builder
Expand Down
4 changes: 2 additions & 2 deletions components/dependency_injection/workflow.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Bundle-level Configuration with Extensions

By convention, each bundle contains an Extension class which is in the bundle's
``DependencyInjection`` directory. These are registered with the ``ContainerBuilder``
when the kernel is booted. When the ``ContainerBuilder`` is :doc:`/compiled<components/dependency-injection/compilation>`,
when the kernel is booted. When the ``ContainerBuilder`` is :doc:`compiled</components/dependency-injection/compilation>`,
the application-level configuration relevant to the bundle's extension is
passed to the Extension which also usually loads its own config file(s), typically from the bundle's
``Resources/config`` directory. The application-level config is usually processed
Expand All @@ -63,7 +63,7 @@ Compiler passes to allow Interaction between Bundles

:ref:`Compiler passes<components-dependency-injection-compiler-passes>` are
used to allow interaction between different bundles as they cannot affect
each others configuration in the extension classes. One of the main uses is
each other's configuration in the extension classes. One of the main uses is
to process tagged services, allowing bundles to register services to picked
up by other bundles, such as Monolog loggers, Twig extensions and Data Collectors
for the Web Profiler. Compiler passes are usually placed in the bundle's
Expand Down