8000 --- · githubfromgui/symfony-docs@96c43c8 · GitHub
[go: up one dir, main page]
Skip to content 8000

Commit 96c43c8

Browse files
javiereguiluzjaviereguiluz
committed
---
yaml --- r: 73431 b: refs/heads/5.x c: 2c24e64 h: refs/heads/5.x i: 73429: 4014ede 73427: 77d3ca0 73423: 02c4376
1 parent 8119968 commit 96c43c8

File tree

7 files changed

+28
-37
lines changed

7 files changed

+28
-37
lines changed

‎[refs]

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,4 +92,4 @@ refs/heads/3.3: 93587037fef6a2f40e0cbdea41754e1e76255fe6
9292
refs/heads/weaverryan-patch-1: a52aee3dceba3357dd59558677811a2ff86d1357
9393
refs/heads/4.0: e887a8b5e5d102235545837506f1d4e883f051a5
9494
refs/heads/4.1: 67f3845bc17a81379c609af1944099706e5b429e
95-
refs/heads/5.x: ca8980edf53ada122195eddabae5e36d01f0bd8d
95+
refs/heads/5.x: 2c24e643569943c397fd381d2db60b4efcde962f

‎trunk/components/lock.rst

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,8 +208,10 @@ Available Stores
208208
----------------
209209

210210
Locks are created and managed in ``Stores``, which are classes that implement
211-
:class:`Symfony\\Component\\Lock\\StoreInterface`. The component includes the
212-
following built-in store types:
211+
:class:`Symfony\\Component\\Lock\\PersistStoreInterface` and, optionally,
212+
:class:`Symfony\\Component\\Lock\\BlockingStoreInterface`.
213+
214+
The component includes the following built-in store types:
213215

214216
============================================ ====== ======== ========
215217
Store Scope Blocking Expiring
@@ -222,6 +224,12 @@ Store Scope Blocking Expiring
222224
:ref:`ZookeeperStore <lock-store-zookeeper>` remote no no
223225
============================================ ====== ======== ========
224226

227+
.. versionadded:: 4.4
228+
229+
The ``PersistStoreInterface`` and ``BlockingStoreInterface`` interfaces were
230+
introduced in Symfony 4.4. In previous versions there was only one interface
231+
called ``Symfony\Component\Lock\StoreInterface``.
232+
225233
.. _lock-store-flock:
226234

227235
FlockStore

‎trunk/components/var_dumper.rst

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -224,13 +224,6 @@ option. Read more about this and other options in
224224
are supported (``Ctrl. + G`` or ``Cmd. + G``, ``F3``, etc.) When
225225
finished, press ``Esc.`` to hide the box again.
226226

227-
If you want to use your browser search input, press ``Ctrl. + F`` or
228-
``Cmd. + F`` again while having focus on VarDumper's search input.
229-
230-
.. versionadded:: 4.4
231-
232-
The feature to use the browser search input was introduced in Symfony 4.4.
233-
234227
Using the VarDumper Component in your PHPUnit Test Suite
235228
--------------------------------------------------------
236229

‎trunk/event_dispatcher.rst

Lines changed: 9 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,12 @@ The most common way to listen to an event is to register an **event listener**::
2727
namespace App\EventListener;
2828

2929
use Symfony\Component\HttpFoundation\Response;
30-
use Symfony\Component\HttpKernel\Event\ExceptionEvent;
30+
use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent;
3131
use Symfony\Component\HttpKernel\Exception\HttpExceptionInterface;
3232

3333
class ExceptionListener
3434
{
35-
public function onKernelException(ExceptionEvent $event)
35+
public function onKernelException(GetResponseForExceptionEvent $event)
3636
{
3737
// You get the exception object from the received event
3838
$exception = $event->getException();
@@ -63,16 +63,10 @@ The most common way to listen to an event is to register an **event listener**::
6363
.. tip::
6464

6565
Each event receives a slightly different type of ``$event`` object. For
66-
the ``kernel.exception`` event, it is :class:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent`.
66+
the ``kernel.exception`` event, it is :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForExceptionEvent`.
6767
Check out the :doc:`Symfony events reference </reference/events>` to see
6868
what type of object each event provides.
6969

70-
.. versionadded::
71-
72-
The :class:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent` class was
73-
introduced in Symfony 4.3. In previous versions it was called
74-
``Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent``.
75-
7670
Now that the class is created, you need to register it as a service and
7771
notify Symfony that it is a "listener" on the ``kernel.exception`` event by
7872
using a special "tag":
@@ -157,7 +151,7 @@ listen to the same ``kernel.exception`` event::
157151
namespace App\EventSubscriber;
158152

159153
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
160-
use Symfony\Component\HttpKernel\Event\ExceptionEvent;
154+
use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent;
161155
use Symfony\Component\HttpKernel\KernelEvents;
162156

163157
class ExceptionSubscriber implements EventSubscriberInterface
@@ -174,17 +168,17 @@ listen to the same ``kernel.exception`` event::
174168
];
175169
}
176170

177-
public function processException(ExceptionEvent $event)
171+
public function processException(GetResponseForExceptionEvent $event)
178172
{
179173
// ...
180174
}
181175

182-
public function logException(ExceptionEvent $event)
176+
public function logException(GetResponseForExceptionEvent $event)
183177
{
184178
// ...
185179
}
186180

187-
public function notifyException(ExceptionEvent $event)
181+
public function notifyException(GetResponseForExceptionEvent $event)
188182
{
189183
// ...
190184
}
@@ -213,11 +207,11 @@ or a "sub request"::
213207
// src/EventListener/RequestListener.php
214208
namespace App\EventListener;
215209

216-
use Symfony\Component\HttpKernel\Event\RequestEvent;
210+
use Symfony\Component\HttpKernel\Event\GetResponseEvent;
217211

218212
class RequestListener
219213
{
220-
public function onKernelRequest(RequestEvent $event)
214+
public function onKernelRequest(GetResponseEvent $event)
221215
{
222216
if (!$event->isMasterRequest()) {
223217
// don't do anything if it's not the master request

‎trunk/frontend.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,6 @@ Other Front-End Articles
109109
.. _`Webpack`: https://webpack.js.org/
110110
.. _`Webpacker`: https://github.com/rails/webpacker
111111
.. _`Mix`: https://laravel.com/docs/mix
112-
.. _`Symfony`: https://symfony.com/
112+
.. _`Symfony`: http://symfony.com/
113113
.. _`Full API`: https://github.com/symfony/webpack-encore/blob/master/index.js
114114
.. _`Webpack Encore screencast series`: https://symfonycasts.com/screencast/webpack-encore

‎trunk/profiler.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,14 +97,14 @@ which provides utilities to profile code and displays the results on the
9797

9898
When using :ref:`autowiring <services-autowire>`, type-hint any argument with
9999
the :class:`Symfony\\Component\\Stopwatch\\Stopwatch` class and Symfony will
100-
inject the Stopwatch service. Then, use the ``start()``, ``lap()`` and
100+
inject the Stopwatch service. Then, use the ``start()``, ``lapse()`` and
101101
``stop()`` methods to measure time::
102102

103103
// a user signs up and the timer starts...
104104
$stopwatch->start('user-sign-up');
105105

106106
// ...do things to sign up the user...
107-
$stopwatch->lap('user-sign-up');
107+
$stopwatch->lapse('user-sign-up');
108108

109109
// ...the sign up process is finished
110110
$stopwatch->stop('user-sign-up');

‎trunk/setup/built_in_web_server.rst

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,16 @@
44
How to Use PHP's built-in Web Server
55
====================================
66

7-
.. deprecated:: 4.4
8-
9-
This article explains how to use the WebServerBundle to run Symfony
10-
applications on your local computer. However, that bundle is deprecated
11-
since Symfony 4.4 and will be removed in Symfony 5.0.
12-
13-
Instead of using WebServerBundle, the preferred way to run your Symfony
14-
applications locally is to use the :doc:`Symfony Local Web Server </setup/symfony_server>`.
15-
167
The PHP CLI SAPI comes with a `built-in web server`_. It can be used to run your
178
PHP applications locally during development, for testing or for application
189
demonstrations. This way, you don't have to bother configuring a full-featured
1910
web server such as :doc:`Apache or Nginx </setup/web_server_configuration>`.
2011

12+
.. tip::
13+
14+
The preferred way to develop your Symfony application is to use
15+
:doc:`Symfony Local Web Server </setup/symfony_server>`.
16+
2117
.. caution::
2218

2319
The built-in web server is meant to be run in a controlled environment.

0 commit comments

Comments
 (0)
0