Fixed ater Wouter's review

symfony · weaverryan · Nov 12, 2017 · Nov 11, 2017 · Nov 12, 2017 · Nov 12, 2017
commit 47a224a9e5d6e38ac4976c2fcfc19cddb3211ce4
diff --git a/bundles/override.rst b/bundles/override.rst
@@ -4,9 +4,9 @@
 How to Override any Part of a Bundle
 ====================================
 
-This document is a quick reference for how to override different parts of
-third-party bundles without using :doc:`/bundles/inheritance`, which was
-removed in Symfony 4.0.
+When using a third-party bundle, you might want to customize or override some of
+its features. This document describes ways of overriding the most common
+features of a bundle.
 
 .. tip::
 

diff --git a/components/console/events.rst b/components/console/events.rst
@@ -97,10 +97,10 @@ thrown by the application.
 Listeners receive a
 :class:`Symfony\\Component\\Console\\Event\\ConsoleExceptionEvent` event::
 
-    use Symfony\Component\Console\Event\ConsoleExceptionEvent;
+    use Symfony\Component\Console\Event\ConsoleErrorEvent;
     use Symfony\Component\Console\ConsoleEvents;
 
-    $dispatcher->addListener(ConsoleEvents::ERROR, function (ConsoleExceptionEvent $event) {
+    $dispatcher->addListener(ConsoleEvents::ERROR, function (ConsoleErrorEvent $event) {
         $output = $event->getOutput();
 
         $command = $event->getCommand();
@@ -111,7 +111,7 @@ Listeners receive a
         $exitCode = $event->getExitCode();
 
         // change the exception to another one
-        $event->setException(new \LogicException('Caught exception', $exitCode, $event->getException()));
+        $event->setException(new \LogicException('Caught exception', $exitCode, $event->getError()));
     });
 
 The ``ConsoleEvents::TERMINATE`` Event

diff --git a/profiler/matchers.rst b/profiler/matchers.rst
@@ -8,3 +8,24 @@ How to Use Matchers to Enable the Profiler Conditionally
 
     The possibility to use a matcher to enable the profiler conditionally was
     removed in Symfony 4.0.
+
+Symfony Profiler cannot be enabled/disabled conditionally using matchers, because
+that feature was removed in Symfony 4.0. However, you can use the ``enable()``
+and ``disable()`` methods of the :class:`Symfony\\Component\\HttpKernel\\Profiler\\Profiler`
+class in your controllers to manage the profiler programmatically::
+
+    use Symfony\Component\HttpKernel\Profiler\Profiler;
+    // ...
+
+    class DefaultController
+    {
+        // ...
+
+        public function someMethod(Profiler $profiler)
+        {
+            // for this particular controller action, the profiler is disabled
+            $profiler->disable();
+
+            // ...
+        }
+    }