Skip to content

Commit 53e4ee9

Browse files
committed
Merge branch '2.8' into 3.2
2 parents 8a150a1 + e70927f commit 53e4ee9

File tree

9 files changed

+20
-9
lines changed

9 files changed

+20
-9
lines changed

bundles/configuration.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ bundle configuration would look like:
8888
http://symfony.com/schema/dic/services/services-1.0.xsd">
8989
9090
<acme-social:config>
91-
<twitter client-id="123" client-secret="your_secret" />
91+
<acme-social:twitter client-id="123" client-secret="your_secret" />
9292
</acme-social:config>
9393
9494
<!-- ... -->

components/console/helpers/formatterhelper.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
Formatter Helper
55
================
66

7-
The Formatter helpers provides functions to format the output with colors.
7+
The Formatter helper provides functions to format the output with colors.
88
You can do more advanced things with this helper than you can in
99
:doc:`/console/coloring`.
1010

components/event_dispatcher.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ the ``Event`` object as the single argument::
182182
}
183183
}
184184

185-
The ``$event`` argument is the event class that was passed when dispatching the
185+
The ``$event`` argument is the event object that was passed when dispatching the
186186
event. In many cases, a special event subclass is passed with extra
187187
information. You can check the documentation or implementation of each event to
188188
determine which instance is passed.

components/phpunit_bridge.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ You can install the component in 2 different ways:
3838
Usage
3939
-----
4040

41-
Once the component installed, it automatically registers a
41+
Once the component is installed, it automatically registers a
4242
`PHPUnit event listener`_ which in turn registers a `PHP error handler`_
4343
called :class:`Symfony\\Bridge\\PhpUnit\\DeprecationErrorHandler`. After
4444
running your PHPUnit tests, you will get a report similar to this one:

components/security/authentication.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ password was valid::
140140
)
141141
);
142142

143-
// for some extra checks: is account enabled, locked, expired, etc.?
143+
// for some extra checks: is account enabled, locked, expired, etc.
144144
$userChecker = new UserChecker();
145145

146146
// an array of password encoders (see below)

configuration/environments.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ behavior:
231231
# 'test' environment and debug disabled
232232
$ php bin/console command_name --env=test --no-debug
233233
234-
In addition to the ``--env`` and ``--debug`` options, the behavior of Symfony
234+
In addition to the ``--env`` and ``--no-debug`` options, the behavior of Symfony
235235
commands can also be controlled with environment variables. The Symfony console
236236
application checks the existence and value of these environment variables before
237237
executing any command:

configuration/micro_kernel_trait.rst

+12-1
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ That's it! To test it, you can start the built-in web server:
8282
8383
Then see the JSON response in your browser:
8484

85-
> http://localhost:8000/random/10
85+
http://localhost:8000/random/10
8686

8787
The Methods of a "Micro" Kernel
8888
-------------------------------
@@ -326,6 +326,17 @@ this:
326326
├─ composer.json
327327
└─ composer.lock
328328
329+
As before you can use PHP built-in server:
330+
331+
.. code-block:: bash
332+
333+
cd web/
334+
$ php -S localhost:8000
335+
336+
Then see webpage in browser:
337+
338+
http://localhost:8000/random/10
339+
329340
Hey, that looks a lot like a *traditional* Symfony application! You're right: the
330341
``MicroKernelTrait`` *is* still Symfony: but you can control your structure and
331342
features quite easily.

event_dispatcher/before_after_filters.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ Creating an Event Listener
101101
~~~~~~~~~~~~~~~~~~~~~~~~~~
102102

103103
Next, you'll need to create an event listener, which will hold the logic
104-
that you want executed before your controllers. If you're not familiar with
104+
that you want to be executed before your controllers. If you're not familiar with
105105
event listeners, you can learn more about them at :doc:`/event_dispatcher`::
106106

107107
// src/AppBundle/EventListener/TokenListener.php

form/dynamic_form_modification.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -303,7 +303,7 @@ and fill in the listener logic::
303303

304304
$formOptions = array(
305305
'class' => User::class,
306-
'property' => 'fullName',
306+
'choice_label' => 'fullName',
307307
'query_builder' => function (EntityRepository $er) use ($user) {
308308
// build a custom query
309309
// return $er->createQueryBuilder('u')->addOrderBy('fullName', 'DESC');

0 commit comments

Comments
 (0)