From a0e3190075b04e6ea53140519899e687ac4b187e Mon Sep 17 00:00:00 2001 From: Anto Date: Wed, 20 Feb 2019 06:58:33 +0100 Subject: [PATCH] Update to output attribute --- core/messenger.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/core/messenger.md b/core/messenger.md index 6f7b694bb87..f3376bfe6a5 100644 --- a/core/messenger.md +++ b/core/messenger.md @@ -34,7 +34,7 @@ use Symfony\Component\Validator\Constraints as Assert; * "post"={"status"=202} * }, * itemOperations={}, - * outputClass=false + * output=false * ) */ final class ResetPasswordRequest @@ -53,7 +53,7 @@ Because the `messenger` attribute is `true`, when a `POST` will be handled by AP For this example, only the `POST` operation is enabled. We use the `status` attribute to configure API Platform to return a [202 Accepted HTTP status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202). It indicates that the request has been received and will be treated later, without giving an immediate return to the client. -Finally, the `output_class` attribute is set to `false`, so the HTTP response that will be generated by API Platform will be empty, and the [serialization process](serialization.md) will be skipped. +Finally, the `output` attribute is set to `false`, so the HTTP response that will be generated by API Platform will be empty, and the [serialization process](serialization.md) will be skipped. ## Registering a Message Handler