Skip to content

[spring-server] support for creating data loader registry per execution #410

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

Merged
merged 1 commit into from
Oct 1, 2019

Conversation

dariuszkuc
Copy link
Collaborator

📝 Description

Instance of DataLoaderRegistry should be created per GraphQL query execution instead of being a singleton. Developers can create their custom instance of DataLoaderRegistry by providing custom DataLoaderRegistryFactory bean.

🔗 Related Issues

#381
#396
#400

Instance of `DataLoaderRegistry` should be created per GraphQL query execution instead of being a singleton. Developers can create their custom instance of `DataLoaderRegistry` by providing custom `DataLoaderRegistryFactory` bean.
@smyrick smyrick added changes: minor Changes require a minor version type: bug Something isn't working labels Oct 1, 2019
@smyrick smyrick merged commit c612b2c into ExpediaGroup:master Oct 1, 2019
@dariuszkuc dariuszkuc deleted the data_loader branch October 1, 2019 17:47
dariuszkuc added a commit to dariuszkuc/graphql-kotlin that referenced this pull request Aug 5, 2022
…on (ExpediaGroup#410)

Instance of `DataLoaderRegistry` should be created per GraphQL query execution instead of being a singleton. Developers can create their custom instance of `DataLoaderRegistry` by providing custom `DataLoaderRegistryFactory` bean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes: minor Changes require a minor version type: bug Something isn't working
Development

Successfully merging this pull request may close these issues.

2 participants