Skip to content
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

[Fusion] Endless Loop if subgraph does not have any types declared #6510

Closed
1 task done
tessarolli opened this issue Sep 6, 2023 · 0 comments · Fixed by #6532
Closed
1 task done

[Fusion] Endless Loop if subgraph does not have any types declared #6510

tessarolli opened this issue Sep 6, 2023 · 0 comments · Fixed by #6532
Assignees
Labels
Area: Fusion Issue is related to Hot Chocolate Fusion 🌶️ hot chocolate
Milestone

Comments

@tessarolli
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Product

Hot Chocolate

Describe the bug

If you have a subgraph which doesnt have any types declared in its schema, like the following:

schema {
  query: Query
  mutation: Mutation
}

type Mutation {
  flightServiceMutationTest: Boolean!
}

type Query {
  flightServiceQueryTest: Boolean!
}

And you compose it on a Fusion Gateway and you query for any valid query or mutation on that subgraph, you will trigger an endless loop on
ExecutionStepDiscoveryMiddleware
Because that Subgraph wont be referenced in FusionGraphConfiguration .

Steps to reproduce

Relevant log output

No response

Additional Context?

If you modify the schema to something that includes an Custom Type, like the one below, then it works.

schema {
  query: Query
  mutation: Mutation
}

type Mutation {
  flightServiceMutationTest: Boolean!
}

type Query {
  flightServiceQueryTest: Boolean!
  myProperty: TestType!
}

type TestType {
  myProperty: Int!
}

Version

13.6.0-preview.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Fusion Issue is related to Hot Chocolate Fusion 🌶️ hot chocolate
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants