@@ -418,7 +418,11 @@ and set a new ``Exception`` object, or do nothing::
418418 response won't work. If you want to overwrite the status code (which you
419419 should not without a good reason), set the ``X-Status-Code `` header::
420420
421- return new Response('Error', 404 /* ignored */, array('X-Status-Code' => 200));
421+ return new Response(
422+ 'Error',
423+ 404 // ignored,
424+ array('X-Status-Code' => 200)
425+ );
422426
423427..index ::
424428 single: Event Dispatcher
@@ -610,11 +614,19 @@ If you enable the web profiler, you also need to mount the profiler routes:
610614
611615 ..code-block ::xml
612616
613- <import resource =" @WebProfilerBundle/Resources/config/routing/profiler.xml" prefix =" /_profiler" />
617+ <import
618+ resource =" @WebProfilerBundle/Resources/config/routing/profiler.xml"
619+ prefix =" /_profiler"
620+ />
614621
615622 ..code-block ::php
616623
617- $collection->addCollection($loader->import("@WebProfilerBundle/Resources/config/routing/profiler.xml"), '/_profiler');
624+ $collection->addCollection(
625+ $loader->import(
626+ "@WebProfilerBundle/Resources/config/routing/profiler.xml"
627+ ),
628+ '/_profiler'
629+ );
618630
619631 As the profiler adds some overhead, you might want to enable it only under
620632certain circumstances in the production environment. The ``only-exceptions ``
@@ -626,7 +638,8 @@ portion of the website? You can use a request matcher:
626638
627639 ..code-block ::yaml
628640
629- # enables the profiler only for request coming for the 192.168.0.0 network
641+ # enables the profiler only for request coming
642+ # for the 192.168.0.0 network
630643framework :
631644profiler :
632645matcher :{ ip: 192.168.0.0/24 }
@@ -641,14 +654,18 @@ portion of the website? You can use a request matcher:
641654profiler :
642655matcher :{ ip: 192.168.0.0/24, path: "^/admin/" }
643656
644- # use a custom matcher instance defined in the "custom_matcher" service
657+ # use a custom matcher instance defined in
658+ # the "custom_matcher" service
645659framework :
646660profiler :
647661matcher :{ service: custom_matcher }
648662
649663 ..code-block ::xml
650664
651- <!-- enables the profiler only for request coming for the 192.168.0.0 network-->
665+ <!--
666+ enables the profiler only for request coming
667+ for the 192.168.0.0 network
668+ -->
652669 <framework : config >
653670 <framework : profiler >
654671 <framework : matcher ip =" 192.168.0.0/24" />
@@ -669,7 +686,10 @@ portion of the website? You can use a request matcher:
669686 </framework : profiler >
670687 </framework : config >
671688
672- <!-- use a custom matcher instance defined in the "custom_matcher" service-->
689+ <!--
690+ use a custom matcher instance defined in
691+ the "custom_matcher" service
692+ -->
673693 <framework : config >
674694 <framework : profiler >
675695 <framework : matcher service =" custom_matcher" />
@@ -678,7 +698,8 @@ portion of the website? You can use a request matcher:
678698
679699 ..code-block ::php
680700
681- // enables the profiler only for request coming for the 192.168.0.0 network
701+ // enables the profiler only for request coming
702+ // for the 192.168.0.0 network
682703 $container->loadFromExtension('framework', array(
683704 'profiler' => array(
684705 'matcher' => array('ip' => '192.168.0.0/24'),
@@ -695,11 +716,15 @@ portion of the website? You can use a request matcher:
695716 // combine rules
696717 $container->loadFromExtension('framework', array(
697718 'profiler' => array(
698- 'matcher' => array('ip' => '192.168.0.0/24', 'path' => '^/admin/'),
719+ 'matcher' => array(
720+ 'ip' => '192.168.0.0/24',
721+ 'path' => '^/admin/',
722+ ),
699723 ),
700724 ));
701725
702- # use a custom matcher instance defined in the "custom_matcher" service
726+ // use a custom matcher instance defined in
727+ // the "custom_matcher" service
703728 $container->loadFromExtension('framework', array(
704729 'profiler' => array(
705730 'matcher' => array('service' => 'custom_matcher'),