From 12f642ee263fc7f101f6c21ce721253b2b0f4b31 Mon Sep 17 00:00:00 2001 From: Haralan Dobrev Date: Sun, 25 Feb 2018 22:00:49 +0200 Subject: [PATCH] Rename missing allowCustomResponseCode to correct allowCustomResponseCode Introduced in https://github.com/symfony/symfony-docs/commit/5f0becf3233238a9d96cba39f3146a0e7ae03763 The functionality was introduced in https://github.com/symfony/symfony/pull/19822. The method got renamed during code review, but was not updated in the docs. https://github.com/symfony/symfony/pull/19822#discussion_r83540504 --- reference/events.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/reference/events.rst b/reference/events.rst index bc5a381fe04..5ea251b7a64 100644 --- a/reference/events.rst +++ b/reference/events.rst @@ -236,15 +236,15 @@ response: If you want to overwrite the status code of the exception response, which you should not without a good reason, call - ``GetResponseForExceptionEvent::allowSuccessfulResponse()`` first and then + ``GetResponseForExceptionEvent::allowCustomResponseCode()`` first and then set the status code on the response:: - $event->allowSuccessfulResponse(); + $event->allowCustomResponseCode(); $response = new Response('No Content', 204); $event->setResponse($response); The status code sent to the client in the above example will be ``204``. If - ``$event->allowSuccessfulResponse()`` is omitted, then the kernel will set + ``$event->allowCustomResponseCode()`` is omitted, then the kernel will set an appropriate status code based on the type of exception thrown. .. seealso::