Circular dependency help

[calm nova]

After upgrading dependencies to newer version I'm not getting a circular dependency when trying to start the project

[eager violet]

⌛ This post has been reserved for your question.

Hey @calm nova! Please use /close or the Close Post button above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.

TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.

[calm nova]

https://pastebin.com/tzuUJNhM

[zealous geode]

Can you show your GraphqlConfiguration (ideally a code block and not a pastebin)

[zealous geode]

so that class has an @Autowired DataFetcherExceptionHandler field

and a DataFetcherExceptionHandler bean method

so you need a DataFetcherExceptionHandler for creating the GraphqlConfiguration

but the DataFetcherExceptionHandler is created by the GraphqlConfiguration

[calm nova]

Right, I thought that was very odd as well, however that issue occurred after the dependency version upgrades

So that's what I'm trying to figure out

My colleagues is still running the project with the older dependency versions

And the project starts just fine

Could it be that for some reason the older dependency versions somehow allowed for circular dependencies to be present?

[zealous geode]

You can try removing the dataFetcherExceptionHandler field and adding it as a parameter to executionStrategyProvider()

[zealous geode]

no idea why that would work with older versions

ohhhhhh

the package name is different

graphql.execution.DataFetcherExceptionHandler vs myteam.app.graphql.exception.DataFetcherExceptionHandler

maybe that somehow made it work in the old versions

[calm nova]

Not sure, I'm following, are you saying that the graphql package name has changed in the new version?

[zealous geode]

That shouldn't be the case but it can be allowed with some configurations (though it's normally a bad idea)

[zealous geode]

No. It seems like your project has a myteam.app.graphql.exception.DataFetcherExceptionHandler that probably extends/implements graphql.exception.DataFetcherExceptionHandler

[calm nova]

Yes, that is true

[zealous geode]

First of all, try that

and if it isn't enough, can you show the myteam.app.graphql.exception.DataFetcherExceptionHandler?

[calm nova]

Sure

Hmm, I'm getting a bunch of new errors now, not sure whether they have to do with the original one or are just brand new ones

[zealous geode]

If you think you can fix them on your own, do that.
If you have further questions, you can still ask here