Skip to content
This repository was archived by the owner on Dec 19, 2023. It is now read-only.

Can't use a GraphQLSchemaProvider with the GraphQLWebAutoConfiguration #192

Closed
ryanjones71 opened this issue Jan 31, 2019 · 4 comments
Closed
Labels

Comments

@ryanjones71
Copy link

Commit 41fe82a changed the GraphQLWebAutoConfiguration from allowing a GraphQLSchemaProvider as an option. How do we continue to use a GraphQLSchemaProvider?

@oliemansm
Copy link
Member

@ryanjones71 The current version in master still supports GraphQLSchemaProvider:

public GraphQLInvocationInputFactory invocationInputFactory(GraphQLSchemaProvider schemaProvider) {
.

@oliemansm
Copy link
Member

Closed due to inactivity.

@juriad
Copy link

juriad commented May 3, 2019

I encountered the same issue. I want to provide my own GraphQLSchemaProvider bean while still using the autoconfiguration. It is not possible since the bean GraphQLSchema doesn't exist (it cannot exist since my schema is dynamic).

@ConditionalOnBean({GraphQLSchema.class})
public class GraphQLWebAutoConfiguration implements ApplicationContextAware {

@Blemicek
Copy link

The issue is also valid for the GraphQLWebsocketAutoConfiguration. The auto configurations should be conditional on GraphQLSchema or GraphQLSchemaProvider.

@oliemansm, could you reopen this issue or should we create a new one?

oliemansm added a commit that referenced this issue Jun 20, 2019
Allowed auto configuration with custom schema provider (fixes #192)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants