Merge pull request #1573 from vincentchalamon/docs/links

fix: links to main

Author: vincentchalamon

core/configuration.md

@@ -27,10 +27,6 @@ api_platform:
     # Specify a path name generator to use.
     path_segment_name_generator: 'api_platform.path_segment_name_generator.underscore'
 
-    # Allow using plain IDs for JSON format.
-    # Deprecated since API Platform 2.7, will be removed in API Platform 3.0
-    allow_plain_identifiers: false
-
     validator:
         # Enable the serialization of payload fields when a validation error is thrown.
         # If you want to serialize only some payload fields, define them like this: [ severity, anotherPayloadField ]
@@ -54,14 +50,6 @@ api_platform:
         # If disabled, it will only join relations having the EAGER fetch mode.
         force_eager: true
 
-    # Enabling the FOSUserBundle integration has been deprecated in 2.5 and will be removed in 3.0.
-    # Enable the FOSUserBundle integration.
-    enable_fos_user: false
-
-    # Enabling the NelmioApiDocBundle integration has been deprecated in 2.2 and will be removed in 3.0.
-    # NelmioApiDocBundle 3 has native support for API Platform.
-    enable_nelmio_api_doc: false
-
     # Enable the Swagger documentation and export.
     enable_swagger: true
 
@@ -103,35 +91,6 @@ api_platform:
             # The name of the query parameter to enable or disable the partial pagination.
             partial_parameter_name: 'partial'
 
-            # To enable or disable pagination for all resource collections by default.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_enabled instead.
-            enabled: true
-
-            # To allow partial pagination for all resource collections.
-            # This improves performances by skipping the `COUNT` query.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_partial instead.
-            partial: false
-
-            # To allow the client to enable or disable the pagination.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_client_enabled instead.
-            client_enabled: false
-
-            # To allow the client to set the number of items per page.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_client_items_per_page instead.
-            client_items_per_page: false
-
-            # To allow the client to enable or disable the partial pagination.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_client_partial instead.
-            client_partial: false
-
-            # The default number of items per page.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_items_per_page instead.
-            items_per_page: 30
-
-            # The maximum number of items per page.
-            # Deprecated since 2.6 and will be removed in 3.0, use defaults.pagination_maximum_items_per_page instead.
-            maximum_items_per_page: ~
-
     mapping:
         # The list of paths with files or directories where the bundle will look for additional resource files.
         paths: []
@@ -256,22 +215,6 @@ api_platform:
             # Use another service as the purger for example "api_platform.http_cache.purger.varnish.xkey"
             purger: 'api_platform.http_cache.purger.varnish.ban'
 
-        # Automatically generate etags for API responses.
-        # Deprecated since 2.6 and will be removed in 3.0, use defaults.cache_headers.etag instead.
-        etag: true
-
-        # Default value for the response max age.
-        # Deprecated since 2.6 and will be removed in 3.0, use defaults.cache_headers.max_age instead.
-        max_age: 3600
-
-        # Default value for the response shared (proxy) max age.
-        # Deprecated since 2.6 and will be removed in 3.0, use defaults.cache_headers.shared_max_age instead.
-        shared_max_age: 3600
-
-        # Default values of the "Vary" HTTP header.
-        # Deprecated since 2.6 and will be removed in 3.0, use defaults.cache_headers.vary instead.
-        vary: ['Accept']
-
     mercure:
         # Enabled by default with installed symfony/mercure-bundle.
         enabled: false

core/events.md

@@ -61,7 +61,7 @@ Attribute      | Type   | Default | Description
 
 Registering your own event listeners to add extra logic is convenient.
 
-The [`ApiPlatform\Core\EventListener\EventPriorities`](https://github.com/api-platform/core/blob/2.6/src/EventListener/EventPriorities.php) class comes with a convenient set of class constants corresponding to commonly used priorities:
+The [`ApiPlatform\Core\EventListener\EventPriorities`](https://github.com/api-platform/core/blob/main/src/Symfony/EventListener/EventPriorities.php) class comes with a convenient set of class constants corresponding to commonly used priorities:
 
 Constant           | Event             | Priority |
 -------------------|-------------------|----------|

core/filters.md

@@ -526,8 +526,6 @@ It will also check the emptiness of a collection association.
 
 Syntax: `?exists[property]=<true|false|1|0>`
 
-Previous syntax (deprecated): `?property[exists]=<true|false|1|0>`
-
 Enable the filter:
 
 [codeSelector]

core/fosuser-bundle.md

@@ -1,16 +1,5 @@
 # FOSUserBundle Integration
 
-## ⚠️ Deprecated: this integration is deprecated and will be removed in API Platform 3
-
-FOSUserBundle is not well suited for APIs. We strongly encourage you to use the [Doctrine user provider](https://symfony.com/doc/current/security/user_provider.html#entity-user-provider)
-shipped with Symfony or to [create a custom user provider](https://symfony.com/doc/current/security/user_provider.html#creating-a-custom-user-provider)
-instead of using this bundle.
-
-API Platform is shipped with a bridge for [FOSUserBundle](https://github.com/FriendsOfSymfony/FOSUserBundle).
-If the FOSUser bundle is enabled, this bridge will use its `UserManager` to create, update and delete user resources.
-
-<p align="center" class="symfonycasts"><a href="https://symfonycasts.com/screencast/api-platform/user-entity?cid=apip"><img src="../distribution/images/symfonycasts-player.png" alt="User Entity screencast"><br>Watch the User Entity screencast</a></p>
-
 ## Installing the Bundle
 
 The installation procedure of the FOSUserBundle is described [in the main Symfony docs](https://symfony.com/doc/master/bundles/FOSUserBundle/index.html)
@@ -31,16 +20,6 @@ framework:
     form: { enabled: true }
 ```
 
-## Enabling the Bridge
-
-To enable the provided bridge with FOSUserBundle, you need to add the following configuration to API Platform:
-
-```yaml
-# api/config/packages/api_platform.yaml
-api_platform:
-    enable_fos_user: true
-```
-
 ## Creating a `User` Entity with Serialization Groups
 
 Here's an example of declaration of a [Doctrine ORM User class](https://github.com/FriendsOfSymfony/FOSUserBundle/blob/master/Resources/doc/index.rst#a-doctrine-orm-user-class).
@@ -65,7 +44,7 @@ use Symfony\Component\Serializer\Annotation\Groups;
 #[ORM\Entity]
 #[ORM\Table(name: 'fos_user')]
 #[ApiResource(
-    normalizationContext: ['groups' => ['user', 'user:read']],
+    normalizationContext: ['groups' => ['user']],
     denormalizationContext: ['groups' => ['user', 'user:write']],
 )]
 class User extends BaseUser

core/identifiers.md

@@ -187,7 +187,7 @@ final class Person
 API Platform supports the following identifier types:
 
 - `scalar` (string, integer)
-- `\DateTime` (uses the symfony `DateTimeNormalizer` internally, see [DateTimeIdentifierNormalizer](https://github.com/api-platform/core/blob/main/src/Api/UuidUriVariableTransformer/DateTimeUriVariableTransformer.php))
-- `\Ramsey\Uuid\Uuid` (see [UuidNormalizer](https://github.com/api-platform/core/blob/main/src/RamseyUuid/UuidUriVariableTransformer/UuidUriVariableTransformer.php))
-- `\Symfony\Component\Uid\Ulid` (see [UlidNormalizer](https://github.com/api-platform/core/blob/main/src/Symfony/UuidUriVariableTransformer/UlidUriVariableTransformer.php))
-- `\Symfony\Component\Uid\Uuid` (see [UuidNormalizer](https://github.com/api-platform/core/blob/main/src/Symfony/UuidUriVariableTransformer/UuidUriVariableTransformer.php))
+- `\DateTime` (uses the symfony `DateTimeNormalizer` internally, see [DateTimeIdentifierNormalizer](https://github.com/api-platform/core/blob/main/src/Api/UriVariableTransformer/DateTimeUriVariableTransformer.php))
+- `\Ramsey\Uuid\Uuid` (see [UuidNormalizer](https://github.com/api-platform/core/blob/main/src/RamseyUuid/UriVariableTransformer/UuidUriVariableTransformer.php))
+- `\Symfony\Component\Uid\Ulid` (see [UlidNormalizer](https://github.com/api-platform/core/blob/main/src/Symfony/UriVariableTransformer/UlidUriVariableTransformer.php))
+- `\Symfony\Component\Uid\Uuid` (see [UuidNormalizer](https://github.com/api-platform/core/blob/main/src/Symfony/UriVariableTransformer/UuidUriVariableTransformer.php))

core/openapi.md

@@ -487,7 +487,7 @@ As described [in the Symfony documentation](https://symfony.com/doc/current/temp
 </html>
 ```
 
-You may want to copy the [one shipped with API Platform](https://github.com/api-platform/core/blob/2.6/src/Bridge/Symfony/Bundle/Resources/views/SwaggerUi/index.html.twig) and customize it.
+You may want to copy the [one shipped with API Platform](https://github.com/api-platform/core/blob/main/src/Symfony/Bundle/Resources/views/SwaggerUi/index.html.twig) and customize it.
 
 ## Compatibility Layer with Amazon API Gateway
 

core/pagination.md

@@ -342,7 +342,7 @@ To know more about cursor-based pagination take a look at [this blog post on med
 
 ## Controlling The Behavior of The Doctrine ORM Paginator
 
-The [PaginationExtension](https://github.com/api-platform/core/blob/2.6/src/Bridge/Doctrine/Orm/Extension/PaginationExtension.php) of API Platform performs some checks on the `QueryBuilder` to guess, in most common cases, the correct values to use when configuring the Doctrine ORM Paginator:
+The [PaginationExtension](https://github.com/api-platform/core/blob/main/src/Doctrine/Orm/Extension/PaginationExtension.php) of API Platform performs some checks on the `QueryBuilder` to guess, in most common cases, the correct values to use when configuring the Doctrine ORM Paginator:
 
 * `$fetchJoinCollection` argument: Whether there is a join to a collection-valued association. When set to `true`, the Doctrine ORM Paginator will perform an additional query, in order to get the correct number of results.
 

core/state-providers.md

@@ -29,7 +29,7 @@ bin/console make:state-provider
 Let's start with a State Provider for the URI: `/blog_posts/{id}`.
 
 First, your `BlogPostProvider` has to implement the
-[`StateProviderInterface`](https://github.com/api-platform/core/blob/main/src/State/StateProviderInterface.php):
+[`ProviderInterface`](https://github.com/api-platform/core/blob/main/src/State/ProviderInterface.php):
 
 ```php
 <?php

core/validation.md

@@ -552,7 +552,7 @@ For example, from [`Regex`](https://symfony.com/doc/4.4/reference/constraints/Re
 For building custom property schema based on custom validation constraints you can create a custom class
 for generating property scheme restriction.
 
-To create property schema, you have to implement the [`PropertySchemaRestrictionMetadataInterface`](https://github.com/api-platform/core/blob/caca7f26b7f22a0abf84390463a1ea47c47d7757/src/Bridge/Symfony/Validator/Metadata/Property/Restriction/PropertySchemaRestrictionMetadataInterface.php).
+To create property schema, you have to implement the [`PropertySchemaRestrictionMetadataInterface`](https://github.com/api-platform/core/blob/main/src/Symfony/Validator/Metadata/Property/Restriction/PropertySchemaRestrictionMetadataInterface.php).
 This interface defines only 2 methods:
 
 * `create`: to create property schema

extra/releases.md

@@ -4,8 +4,8 @@ API Platform follows the [Semantic Versioning](https://semver.org) strategy.
 
 Only 3 versions are maintained at the same time:
 
-* **stable** (currently the **2.6** branch): regular bug fixes are integrated in this version
-* **old-stable** (currently **2.5** branch): security fixes are integrated in this version, regular bug fixes are **not** backported in it
+* **stable** (currently the **2.7** branch): regular bug fixes are integrated in this version
+* **old-stable** (currently **2.6** branch): security fixes are integrated in this version, regular bug fixes are **not** backported in it
 * **development** (**main** branch): new features target this branch
 
 Older versions (1.x, 2.0...) **are not maintained**. If you still use them, you must upgrade as soon as possible.