@@ -1855,7 +1855,7 @@ Multiple parameters targeting the same relation path share the same JOIN (ORM) o
 ### Nested Properties with the Legacy ApiFilter Syntax (deprecated)
 
 > [!WARNING] The legacy method using the `ApiFilter` attribute is **deprecated** and scheduled for
-> **removal** in API Platform **5.0**. We strongly recommend migrating to the new `QueryParameter`
+> **removal** in API Platform **6.0**. We strongly recommend migrating to the new `QueryParameter`
 > syntax described above.
 
 For legacy code, the built-in filters that extend `AbstractFilter` support nested properties using
@@ -1921,7 +1921,7 @@ The above allows you to find offers by their respective product's color:
 ## Enabling a Filter for All Properties of a Resource
 
 > [!WARNING] The legacy method using the `ApiFilter` attribute is **deprecated** and scheduled for
-> **removal** in API Platform **5.0**. We strongly recommend migrating to the new `QueryParameter`
+> **removal** in API Platform **6.0**. We strongly recommend migrating to the new `QueryParameter`
 > syntax, which is detailed in the [Introduction](#introduction). You can use the `:property`
 > placeholder instead and it is recommended to use a filter for each type of data you are filtering.
 
@@ -2287,7 +2287,7 @@ use Doctrine\ORM\QueryBuilder;
 
 class MyCustomFilter implements FilterInterface
 {
-    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.
+    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.
 
     public function apply(QueryBuilder $queryBuilder, QueryNameGeneratorInterface $queryNameGenerator, string $resourceClass, ?Operation $operation = null, array $context = []): void
     {
@@ -2308,6 +2308,12 @@ class MyCustomFilter implements FilterInterface
 }
 ```
 
+`BackwardCompatibleFilterDescriptionTrait` supplies a `getDescription()` method that returns an
+empty array, satisfying the legacy `FilterInterface::getDescription()` requirement without you
+having to implement it by hand. It lets a custom filter keep working with the deprecated filter
+chain while you migrate it to `#[QueryParameter]`, and it will be removed in API Platform 6.0
+together with `getDescription()` itself.
+
 #### Implementing a Custom ORM Filter
 
 Let's create a concrete filter that allows fetching entities based on the month of a date field (for
@@ -2334,7 +2340,7 @@ use Doctrine\ORM\QueryBuilder;
 
 class MonthFilter implements FilterInterface
 {
-    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.
+    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.
 
     public function apply(QueryBuilder $queryBuilder, QueryNameGeneratorInterface $queryNameGenerator, string $resourceClass, ?Operation $operation = null, array $context = []): void
     {
@@ -2578,7 +2584,7 @@ use Doctrine\ODM\MongoDB\Aggregation\Builder;
 
 class MonthFilter implements FilterInterface
 {
-    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.
+    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.
 
     public function apply(Builder $aggregationBuilder, string $resourceClass, ?Operation $operation = null, array &$context = []): void
     {
@@ -2620,7 +2626,7 @@ use Doctrine\ODM\MongoDB\Aggregation\Builder;
 
 class MonthFilter implements FilterInterface
 {
-    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.
+    use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.
 
     public function apply(Builder $aggregationBuilder, string $resourceClass, ?Operation $operation = null, array &$context = []): void
     {
Original file line number	Diff line number	Diff line change
`@@ -1855,7 +1855,7 @@ Multiple parameters targeting the same relation path share the same JOIN (ORM) o`
`1855`	`1855`	`### Nested Properties with the Legacy ApiFilter Syntax (deprecated)`
`1856`	`1856`
`1857`	`1857`	> [!WARNING] The legacy method using the `ApiFilter` attribute is deprecated and scheduled for
`1858`		-> removal in API Platform 5.0. We strongly recommend migrating to the new `QueryParameter`
	`1858`	+> removal in API Platform 6.0. We strongly recommend migrating to the new `QueryParameter`
`1859`	`1859`	`> syntax described above.`
`1860`	`1860`
`1861`	`1861`	For legacy code, the built-in filters that extend `AbstractFilter` support nested properties using
`@@ -1921,7 +1921,7 @@ The above allows you to find offers by their respective product's color:`
`1921`	`1921`	`## Enabling a Filter for All Properties of a Resource`
`1922`	`1922`
`1923`	`1923`	> [!WARNING] The legacy method using the `ApiFilter` attribute is deprecated and scheduled for
`1924`		-> removal in API Platform 5.0. We strongly recommend migrating to the new `QueryParameter`
	`1924`	+> removal in API Platform 6.0. We strongly recommend migrating to the new `QueryParameter`
`1925`	`1925`	> syntax, which is detailed in the [Introduction](#introduction). You can use the `:property`
`1926`	`1926`	`> placeholder instead and it is recommended to use a filter for each type of data you are filtering.`
`1927`	`1927`
`@@ -2287,7 +2287,7 @@ use Doctrine\ORM\QueryBuilder;`
`2287`	`2287`
`2288`	`2288`	`class MyCustomFilter implements FilterInterface`
`2289`	`2289`	`{`
`2290`		`- use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.`
	`2290`	`+ use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.`
`2291`	`2291`
`2292`	`2292`	`public function apply(QueryBuilder $queryBuilder, QueryNameGeneratorInterface $queryNameGenerator, string $resourceClass, ?Operation $operation = null, array $context = []): void`
`2293`	`2293`	`{`
`@@ -2308,6 +2308,12 @@ class MyCustomFilter implements FilterInterface`
`2308`	`2308`	`}`
`2309`	`2309`	```
`2310`	`2310`
	`2311`	+`BackwardCompatibleFilterDescriptionTrait` supplies a `getDescription()` method that returns an
	`2312`	+empty array, satisfying the legacy `FilterInterface::getDescription()` requirement without you
	`2313`	`+having to implement it by hand. It lets a custom filter keep working with the deprecated filter`
	`2314`	+chain while you migrate it to `#[QueryParameter]`, and it will be removed in API Platform 6.0
	`2315`	+together with `getDescription()` itself.
	`2316`	`+`
`2311`	`2317`	`#### Implementing a Custom ORM Filter`
`2312`	`2318`
`2313`	`2319`	`Let's create a concrete filter that allows fetching entities based on the month of a date field (for`
`@@ -2334,7 +2340,7 @@ use Doctrine\ORM\QueryBuilder;`
`2334`	`2340`
`2335`	`2341`	`class MonthFilter implements FilterInterface`
`2336`	`2342`	`{`
`2337`		`- use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.`
	`2343`	`+ use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.`
`2338`	`2344`
`2339`	`2345`	`public function apply(QueryBuilder $queryBuilder, QueryNameGeneratorInterface $queryNameGenerator, string $resourceClass, ?Operation $operation = null, array $context = []): void`
`2340`	`2346`	`{`
`@@ -2578,7 +2584,7 @@ use Doctrine\ODM\MongoDB\Aggregation\Builder;`
`2578`	`2584`
`2579`	`2585`	`class MonthFilter implements FilterInterface`
`2580`	`2586`	`{`
`2581`		`- use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.`
	`2587`	`+ use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.`
`2582`	`2588`
`2583`	`2589`	`public function apply(Builder $aggregationBuilder, string $resourceClass, ?Operation $operation = null, array &$context = []): void`
`2584`	`2590`	`{`
`@@ -2620,7 +2626,7 @@ use Doctrine\ODM\MongoDB\Aggregation\Builder;`
`2620`	`2626`
`2621`	`2627`	`class MonthFilter implements FilterInterface`
`2622`	`2628`	`{`
`2623`		`- use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 5.0.`
	`2629`	`+ use BackwardCompatibleFilterDescriptionTrait; // Here for backward compatibility, keep it until 6.0.`
`2624`	`2630`
`2625`	`2631`	`public function apply(Builder $aggregationBuilder, string $resourceClass, ?Operation $operation = null, array &$context = []): void`
`2626`	`2632`	`{`