Skip to content

Nested DataLoaders are not dispatched during mutations #8261

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

Open
dannyheard7 opened this issue Apr 24, 2025 · 0 comments
Open

Nested DataLoaders are not dispatched during mutations #8261

dannyheard7 opened this issue Apr 24, 2025 · 0 comments

Comments

@dannyheard7
Copy link
Contributor

dannyheard7 commented Apr 24, 2025

Product

Hot Chocolate

Version

15.1.3

Link to minimal reproduction

https://github.com/dannyheard7/NestedDataLoaderNotDispatchedInMutation

Steps to reproduce

Run the application and send the following mutation:

mutation {
    addProductCatalog(input:  {
       id: 1
    })
}

What is expected?

The GetProductByIdAsync dataloader is dispatched from GetProductCatalogByIdAsync instantly

What is actually happening?

The GetProductByIdAsync never dispatches/takes a very long time to dispatch.

Additional context

The following query runs the same code, however in this case the nested data loader is dispatched instantly

query {
  productCatalog(id: 1) {
    id
  }
}
@dannyheard7 dannyheard7 changed the title Nested DataLoaders are not dispatched during mutations Nested DataLoaders in an intermediary service are not dispatched during mutations Apr 24, 2025
@dannyheard7 dannyheard7 changed the title Nested DataLoaders in an intermediary service are not dispatched during mutations Nested DataLoaders are not dispatched during mutations Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant