@@ -10,7 +10,6 @@ to it::
10
10
namespace Simplex;
11
11
12
12
use Symfony\Component\EventDispatcher\EventDispatcher;
13
- use Symfony\Component\HttpFoundation;
14
13
use Symfony\Component\HttpFoundation\RequestStack;
15
14
use Symfony\Component\HttpKernel;
16
15
use Symfony\Component\Routing;
@@ -199,6 +198,7 @@ Now, here is how you can register a custom listener in the front controller::
199
198
200
199
// ...
201
200
use Simplex\StringResponseListener;
201
+ use Symfony\Component\DependencyInjection\Reference;
202
202
203
203
$container->register('listener.string_response', StringResponseListener::class);
204
204
$container->getDefinition('dispatcher')
@@ -217,7 +217,7 @@ These parameters can be used when defining object definitions. Let's make the
217
217
charset configurable::
218
218
219
219
// ...
220
- $container->register('listener.response', HttpKernel\EventListener\ResponseListener::class)
220
+ $container->register('listener.response', Symfony\Component\ HttpKernel\EventListener\ResponseListener::class)
221
221
->setArguments(['%charset%'])
222
222
;
223
223
@@ -230,7 +230,7 @@ Instead of relying on the convention that the routes are defined by the
230
230
``$routes `` variables, let's use a parameter again::
231
231
232
232
// ...
233
- $container->register('matcher', Routing\Matcher\UrlMatcher::class)
233
+ $container->register('matcher', Symfony\Component\ Routing\Matcher\UrlMatcher::class)
234
234
->setArguments(['%routes%', new Reference('context')])
235
235
;
236
236
0 commit comments