Skip to content

Conversation

KDederichs
Copy link
Contributor

Q A
Branch? 3.0
Tickets n/a
License MIT
Doc PR n/a

As mentioned in #5289 , only use ValueResolverInterface if it exists, use the old one otherwise

@KDederichs
Copy link
Contributor Author

Hmm it still seems to load the old one, I'll look into why more tomorrow

@KDederichs KDederichs force-pushed the fix/value_resolver_interface branch from 3a7aa16 to b94c87c Compare January 12, 2023 10:14
@soyuka
Copy link
Member

soyuka commented Jan 12, 2023

I like this approach better, can you rebase so that the CI runs lowest?

NicoHaase and others added 2 commits January 12, 2023 16:17
…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>
@KDederichs
Copy link
Contributor Author

Hmm looks like there's something else broken in the lowest tests (unrelated to this)
I'll try to get rid of that I guess

@KDederichs KDederichs force-pushed the fix/value_resolver_interface branch from 17ddc27 to 376e2ee Compare January 12, 2023 15:49
@soyuka
Copy link
Member

soyuka commented Jan 12, 2023

No problem, I see that and the exception related to this is gone! We should investigate the other issue in another patch.

@soyuka
Copy link
Member

soyuka commented Jan 12, 2023

whoops the rebase was wrong I did that at #5334

When rebasing against a branch upstream:

git fetch upstream
git rebase upstream/3.0 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants