Add show_webby option

core/configuration.md

@@ -14,6 +14,9 @@ api_platform:
 
     # The version of the API.
     version: '0.0.0'
+
+    # Set this to false if you want Webby to disappear.
+    show_webby: true
 
     # Specify a name converter to use.
     name_converter: ~

core/design.md

@@ -33,10 +33,10 @@ For [Rapid Application Development](https://en.wikipedia.org/wiki/Rapid_applicat
 ORM's data provider and persister implementations shipped with API Platform.
 
 In this case, the public (`@ApiResource`) and internal (Doctrine entity) data model are shared. Then, API Platform will
-be able to query, filter, paginate and persist automatically data.
-This is approach is super-convenient and efficient, but is probably **not a good idea** for non-[CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete)
+be able to query, filter, paginate and persist data automatically.
+This approach is super-convenient and efficient, but is probably **not a good idea** for non-[CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete)
 and/or large systems.
-Again, it's up to the developers to use, or to not use those built-in data providers/persisters depending of the business
+Again, it's up to the developers to use, or to not use these built-in data providers/persisters depending on the business logic
 they are dealing with. API Platform makes it easy to create custom data providers and persisters, and to implement appropriate
 patterns such as [CQS](https://www.martinfowler.com/bliki/CommandQuerySeparation.html) or [CQRS](https://martinfowler.com/bliki/CQRS.html).
 

core/errors.md

@@ -1,6 +1,6 @@
 # Errors Handling
 
-API Platform comes with a powerful error system. It handles excepted (such as faulty JSON documents sent by the
+API Platform comes with a powerful error system. It handles expected (such as faulty JSON documents sent by the
 client or validation errors) as well as unexpected errors (PHP exceptions and errors).
 API Platform automatically sends the appropriate HTTP status code to the client: `400` for expected errors, `500` for
 unexpected ones. It also provides a description of the error in [the Hydra error format](http://www.hydra-cg.com/spec/latest/core/#description-of-http-status-codes-and-errors)

core/file-upload.md

@@ -101,11 +101,8 @@ use App\Entity\MediaObject;
 use App\Form\MediaObjectType;
 use Sensio\Bundle\FrameworkExtraBundle\Configuration\IsGranted;
 use Symfony\Bridge\Doctrine\RegistryInterface;
-use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
 use Symfony\Component\Form\FormFactoryInterface;
 use Symfony\Component\HttpFoundation\Request;
-use Symfony\Component\HttpFoundation\Response;
-use Symfony\Component\Serializer\SerializerInterface;
 use Symfony\Component\Validator\Validator\ValidatorInterface;
 
 final class CreateMediaObjectAction

core/getting-started.md

@@ -99,7 +99,7 @@ use Doctrine\ORM\Mapping as ORM;
 use Symfony\Component\Validator\Constraints as Assert;
 
 /**
- * An offer from my shop - this description will be automatically extracted form the PHPDoc to document the API.
+ * An offer from my shop - this description will be automatically extracted from the PHPDoc to document the API.
  *
  * @ApiResource(iri="http://schema.org/Offer")
  * @ORM\Entity

core/identifiers.md

@@ -20,7 +20,7 @@ use App\Uuid;
  */
 final class Person {
     /**
-     * @type Uuid
+     * @var Uuid
      * @ApiProperty(identifier=true)
      */
     public $code;
@@ -119,5 +119,5 @@ Your `PersonDataProvider` will now work as expected!
 ApiPlatform supports the following identifier types:
 
   - `scalar` (string, integer)
-  - `\DateTime` (uses the symfony `DateTimeNormalizer` internally, see [DateTimeIdentifierNormalizer](https://github.com/api-platform/core/blob/master/src/Identifier/Normalizer/DateTimeIdentifierNormalizer.php))
+  - `\DateTime` (uses the symfony `DateTimeNormalizer` internally, see [DateTimeIdentifierNormalizer](https://github.com/api-platform/core/blob/master/src/Identifier/Normalizer/DateTimeIdentifierDenormalizer.php))
   - `\Ramsey\Uuid\Uuid` (see [UuidNormalizer](https://github.com/api-platform/core/blob/master/src/Bridge/RamseyUuid/Identifier/Normalizer/UuidNormalizer.php))

core/operations.md

@@ -468,19 +468,18 @@ The `subresourceOperations` attribute also allows you to add an access control o
 
 ```php
 <?php
-// api/src/Entity/Question.php
+// api/src/Entity/Answer.php
 
 /**
  * ...
  * @ApiResource(
  *     subresourceOperations={
- *          "answer_get_subresource"= {
- *              "method"="GET",
+ *          "api_questions_answer_get_subresource"= {
  *              "access_control"="has_role('ROLE_AUTHENTICATED')"
  *          }
  *      }
  * )
- class Question
+ class Answer
  {
  }
 ```
@@ -740,7 +739,7 @@ Or in XML:
 #### Entity Retrieval
 
 If you want to bypass the automatic retrieval of the entity in your custom operation, you can set the parameter
-`_api_receive` to `false` in the `default` attribute:
+`_api_receive` to `false` in the `defaults` attribute:
 
 ```php
 <?php

core/validation.md

@@ -7,7 +7,7 @@ if you want to.
 
 ## Validating Submitted Data
 
-Validating submitted data is simple as adding [Symfony's built-in constraints](http://symfony.com/doc/current/reference/constraints.html)
+Validating submitted data is as simple as adding [Symfony's built-in constraints](http://symfony.com/doc/current/reference/constraints.html)
 or [custom constraints](http://symfony.com/doc/current/validation/custom_constraint.html) directly in classes marked with
 the `@ApiResource` annotation:
 

schema-generator/configuration.md

@@ -57,6 +57,9 @@ Supported cardinalities are:
 * `(0..*)`: array, not required
 * `(1..1)`: scalar, required
 * `(1..*)`: array, required
+* `(*..0)`
+* `(*..1)`
+* `(*..*)`
 
 Cardinalities are enforced by the class generator, the Doctrine ORM generator and the Symfony validation generator.