Skip to content

[Cookbook][Bundles][Extension] Fix typos and improve readability #2252

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.

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
Feb 23, 2013
Merged
Changes from all commits
Commits
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
17 changes: 9 additions & 8 deletions cookbook/bundles/extension.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ as integration of other related components:

framework:
# ...
form: true
form: true

.. code-block:: xml

Expand All @@ -33,7 +33,7 @@ as integration of other related components:

$container->loadFromExtension('framework', array(
// ...
'form' => true,
'form' => true,
// ...
));

Expand Down Expand Up @@ -494,9 +494,10 @@ be output to the console in yaml.

As long as your bundle's configuration is located in the standard location
(``YourBundle\DependencyInjection\Configuration``) and does not have a
``__constructor()`` it will work automatically. If you have a something
different your ``Extension`` class will have to override the
``Extension::getConfiguration()`` method. Have it return an instance of your
``__construct()`` it will work automatically. If you have something
different, your ``Extension`` class must override the
:method:`Extension::getConfiguration() <Symfony\\Component\\HttpKernel\\DependencyInjection\\Extension::getConfiguration>`
method and return an instance of your
``Configuration``.

Comments and examples can be added to your configuration nodes using the
Expand Down Expand Up @@ -548,9 +549,9 @@ When creating an extension, follow these simple conventions:
* The extension should provide an XSD schema.

If you follow these simple conventions, your extensions will be registered
automatically by Symfony2. If not, override the Bundle
:method:`Symfony\\Component\\HttpKernel\\Bundle\\Bundle::build` method in
your bundle::
automatically by Symfony2. If not, override the
:method:`Bundle::build() <Symfony\\Component\\HttpKernel\\Bundle\\Bundle::build>`
method in your bundle::

// ...
use Acme\HelloBundle\DependencyInjection\UnconventionalExtensionClass;
Expand Down