8000 Patch based 2.7 by franciscocorrales · Pull Request #6985 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

Patch based 2.7 #6985

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

Closed
wants to merge 5 commits into from
Closed

Patch based 2.7 #6985

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d1d761c
Update inheritance.rst
Sep 20, 2016
a25876c
Update installation.rst
Sep 20, 2016
bb215cb
Update override.rst
Sep 20, 2016
ef674dc
Update prepend_extension.rst
Sep 20, 2016
5fdb433
Update installation.rst
Sep 21, 2016
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
Prev Previous commit
Next Next commit
Update override.rst 
The word 'or' is clear. / not so much.
  • Loading branch information
Francisco Corrales Morales authored Sep 20, 2016
commit bb215cb2aed17d7b7472b485979375ae8571236c
19 changes: 9 additions & 10 deletions bundles/override.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ If the controller is a service, see the next section on how to override it.
Services & Configuration
------------------------

In order to override/extend a service, there are two options. First, you can
In order to override or extend a service you have two options. First, you can
set the parameter holding the service's class name to your own class by setting
it in ``app/config/config.yml``. This of course is only possible if the class name is
defined as a parameter in the service config of the bundle containing the
Expand Down Expand Up @@ -105,17 +105,16 @@ associations. Learn more about this feature and its limitations in
Forms
-----

In order to override a form type, it has to be registered as a service (meaning
it is tagged as ``form.type``). You can then override it as you would override any
service as explained in `Services & Configuration`_. This, of course, will only
work if the type is referred to by its alias rather than being instantiated,
e.g.::
Form types are referred to by their fully-qualified class name::
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only true for Symfony >= 2.8.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But we may want to remove this paragraph entirely for the 2.7 docs and only talk about form type extensions.


$builder->add('name', 'custom_type');
$builder->add('name', CustomType::class);

rather than::
This means that you cannot override this by creating a sub-class of ``CustomType``
and registering it as a service and tagging it with ``form.type`` (you *could*
do this in an earlier version).

$builder->add('name', new CustomType());
Instead, you should use a "form type extension" to modify the existing form type.
For more information, see :doc:`/form/create_form_type_extension`.

.. _override-validation:

Expand All @@ -126,7 +125,7 @@ Symfony loads all validation configuration files from every bundle and
combines them into one validation metadata tree. This means you are able to
add new constraints to a property, but you cannot override them.

To override this, the 3rd party bundle needs to have configuration for
To overcome this, the 3rd party bundle needs to have configuration for
:doc:`validation groups </validation/groups>`. For instance, the FOSUserBundle
has this configuration. To create your own validation, add the constraints
to a new validation group:
Expand Down
0