Merge branch '2.0'

Author: GuilhemN

UPGRADING-2.0.md

@@ -1,40 +1,56 @@
 Upgrading From 1.x To 2.0
 =========================
 
- * The `RedirectView` and `RouteRedirect` view classes were removed. Use `View::createRedirect()`
-   and `View::createRouteRedirect()` instead.
+ * The `RedirectView` and `RouteRedirect` view classes were removed. Use
+   `View::createRedirect()` and `View::createRouteRedirect()` instead.
 
-   **Note**: the default status code for a route redirect has changed from HTTP_CREATED (201) to
-   HTTP_FOUND (302).
+   **Note**: the default status code for a route redirect has changed from
+   HTTP_CREATED (201) to HTTP_FOUND (302).
 
- * The `FOS\RestBundle\Util\ViolationFormatter` class and the `FOS\RestBundle\Util\ViolationFormatterInterface`
-   were removed. Catch specialized exception classes instead of checking specific exception messages.
+ * The `FOS\RestBundle\Util\ViolationFormatter` class and the
+   `FOS\RestBundle\Util\ViolationFormatterInterface` were removed.
+   Catch specialized exception classes instead of checking specific
+   exception messages.
 
- * The `ViolationFormatterInterface` argument of the constructor of the `ParamFetcher` class was
-   removed.
+ * The `ViolationFormatterInterface` argument of the constructor of
+   the `ParamFetcher` class was removed.
 
- * The SensioFrameworkExtraBundle view annotations must be enabled to use the `ViewResponseListener`:
+ * The SensioFrameworkExtraBundle view annotations must be enabled to
+   use the `ViewResponseListener`:
 
-   ```yaml
+   ```yml
    # app/config/config.yml
    sensio_framework_extra:
        view:
            annotations: true
    ```
 
- * dropped support for the legacy ``Symfony\Component\Validator\ValidatorInterface``
+ * dropped support for the legacy
+   `Symfony\Component\Validator\ValidatorInterface`
 
- * removed ``FOS\RestBundle\Util\Codes`` in favor of ``Symfony\Component\HttpFoundation\Response`` constants
+ * removed `FOS\RestBundle\Util\Codes` in favor of
+   `Symfony\Component\HttpFoundation\Response` constants
 
- * compatibility with Symfony <2.7, JMS Serializer/SerializerBundle <1.0 and SensioFrameworkExtraBundle <3.0 was dropped
+ * compatibility with Symfony <2.7, JMS Serializer/SerializerBundle <1.0
+   and SensioFrameworkExtraBundle <3.0 was dropped
 
  * constructor signature of DisableCSRFExtension was changed
 
- * constructor signatures of most of the classes which used the container were changed
+ * constructor signatures of most of the classes which used the container
+   were changed
+
+ * removed `callback_filter` configuration option for the `jsonp_handler`
+
+ * removed `fos_rest.format_listener.media_type` configuration option.
+   Use the versioning section instead:
+
+   ```yml
+   # config.yml
 
- * removed ``callback_filter`` configuration option for the jsonp_handler
+   versioning: true
+   ```
 
- * the ``exception_wrapper_handler`` config option was removed. Use normalizers instead.
+ * the `exception_wrapper_handler` config option was removed. Use normalizers instead.
 
    Before:
    ```yml
@@ -85,9 +101,10 @@ Upgrading From 1.x To 2.0
    }
    ```
 
- * removed all ``.class`` parameters, instead overwriting services via explicit Bundle configuration is preferred
+ * removed all `.class` parameters, instead overwriting services via
+   explicit Bundle configuration is preferred
 
- * renamed ``AbstractScalarParam::$array`` to ``AbstractScalarParam::$map``
+ * renamed `AbstractScalarParam::$array` to `AbstractScalarParam::$map`
 
    Before:
    ```php
@@ -123,16 +140,20 @@ Upgrading From 1.x To 2.0
 
  * added `ControllerTrait` for developers that prefer to use DI for their controllers instead of extending ``FOSRestController``
 
- * when having an action called ``lockUserAction``, then it will have to use the http method ``LOCK`` (RFC-2518) instead of ``PATCH``. The following methods are affected by this change
-   * ``COPY``
-   * ``LOCK``
-   * ``MKCOL``
-   * ``MOVE``
-   * ``PROPFIND``
-   * ``PROPPATCH``
-   * ``UNLOCK``
+ * when having an action called ``lockUserAction``, then it will have to
+   use the http method ``LOCK`` (RFC-2518) instead of ``PATCH``.
+   The following methods are affected by this change:
+
+   * `COPY`
+   * `LOCK`
+   * `MKCOL`
+   * `MOVE`
+   * `PROPFIND`
+   * `PROPPATCH`
+   * `UNLOCK`
 
- * removed the ability of the ``AccessDeniedListener`` to render a response. Use the FOSRestBundle or the twig exception controller in complement.
+ * removed the ability of the `AccessDeniedListener` to render a response.
+   Use the FOSRestBundle or the twig exception controller in complement.
 
    Before:
    ```yml
@@ -151,11 +172,14 @@ Upgrading From 1.x To 2.0
        exception: true # Activates the FOSRestBundle exception controller
    ```
 
- * changed the priority of ``RequestBodyParamConverter`` to ``-50``
+ * changed the priority of `RequestBodyParamConverter` to `-50`
 
- * made silent the ``RequestBodyParamConverter`` when a parameter is optional and it can't resolve it
+ * made silent the `RequestBodyParamConverter` when a parameter is
+   optional and it can't resolve it
 
- * removed the ``format_negotiator`` option ``exception_fallback_format``; you can match the ``ExceptionController`` thanks to the ``attributes`` option instead
+ * removed the `format_negotiator` option `exception_fallback_format`;
+   you can match the `ExceptionController` thanks to the `attributes`
+   option instead
 
    Before:
    ```yml
@@ -178,7 +202,9 @@ Upgrading From 1.x To 2.0
               - { path: ^/, fallback_format: html } }
    ```
 
- * `View::setSerializationContext` and `View::getSerializationContext` have been removed. Use `View::setContext` and `View::getContext` together with the new Context class instead.
+ * `View::setSerializationContext` and `View::getSerializationContext`
+   have been removed. Use `View::setContext` and `View::getContext`
+   together with the new Context class instead.
 
    Before:
    ```php