You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested the new MaxDepth annotation in the Symfony serializer (see #17113). Consider some code that extends the example code given in the pull request with more levels (4, 5, etc.). By keeping a max depth of 2, the result is the following:
As you can see, it considers all child nodes and does not stop after the configured max depths. Only the data of the objects in deeper levels is excluded (attribute foo).
The text was updated successfully, but these errors were encountered:
Okay sorry, my bad. I ran into this issue, because I was debugging a problem with circular references which I tried to solve by setting a max depth. As it did not work, I used your example code for further tests. I just oversaw that the MaxDepth was set on the wrong property.
I tested the new MaxDepth annotation in the Symfony serializer (see #17113). Consider some code that extends the example code given in the pull request with more levels (4, 5, etc.). By keeping a max depth of 2, the result is the following:
As you can see, it considers all child nodes and does not stop after the configured max depths. Only the data of the objects in deeper levels is excluded (attribute foo).
The text was updated successfully, but these errors were encountered: