-
-
Notifications
You must be signed in to change notification settings - Fork 932
chore(deprecation): Only use ValueResolverInterface if it exists #5324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deprecation): Only use ValueResolverInterface if it exists #5324
Conversation
Hmm it still seems to load the old one, I'll look into why more tomorrow |
src/Symfony/Bundle/ArgumentResolver/PayloadArgumentResolver.php
Outdated
Show resolved
Hide resolved
src/Symfony/Bundle/ArgumentResolver/PayloadArgumentResolver.php
Outdated
Show resolved
Hide resolved
3a7aa16
to
b94c87c
Compare
I like this approach better, can you rebase so that the CI runs lowest? |
…form#5314) * test: add reproducer for bug 5310 * fix(graphql): use depth for nested resource class operation Co-authored-by: Alan Poulain <contact@alanpoulain.eu>
Hmm looks like there's something else broken in the lowest tests (unrelated to this) |
17ddc27
to
376e2ee
Compare
No problem, I see that and the exception related to this is gone! We should investigate the other issue in another patch. |
whoops the rebase was wrong I did that at #5334 When rebasing against a branch upstream:
|
As mentioned in #5289 , only use
ValueResolverInterface
if it exists, use the old one otherwise