3cb5619216
This PR was squashed before being merged into the 4.1-dev branch (closes #26108).
Discussion
----------
[Serializer] Add a MaxDepth handler
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | no
| New feature? | yes <!-- don't forget to update src/**/CHANGELOG.md files -->
| BC breaks? | no
| Deprecations? | no <!-- don't forget to update UPGRADE-*.md files -->
| Tests pass? | yes
| Fixed tickets | api-platform/core#1130, api-platform/core#1528, api-platform/core#1528 <!-- #-prefixed issue number(s), if any -->
| License | MIT
| Doc PR | todo <!--highly recommended for new features-->
Sometimes, instead of just stopping the serialization process when the configured max depth is reached, it can be interesting to let the user return something (like returning the identifier of the entity to stop manually the serialization process).
This PR also makes the max depth handling more similar to circular references handling (that already has the possibility to set a handler).
Commits
-------
|
||
|---|---|---|
| .. | ||
| CacheWarmer | ||
| Command | ||
| Console | ||
| Controller | ||
| DependencyInjection | ||
| EventListener | ||
| Fixtures | ||
| Functional | ||
| Kernel | ||
| Routing | ||
| Templating | ||
| Translation | ||
| ClientTest.php | ||
| TestCase.php | ||