spring-projects / spring-projects/spring-graphql
Looking for advice on DGS DataLoader migration
Open
@rstoyanchev is already working on this.
Since Jul 17, 2025.
type: enhancement
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 336
- PR merge metrics
- No merged PRs in 30d
Description
Hi Spring GraphQL Team,
We're migrating from Netflix DGS to Spring GraphQL and have questions about DataLoader.
@SchemaMappingArgument Resolution Validation: When using a DataLoader within a@SchemaMappingmethod, how can we ensure mismatches between the DataLoader name (registered viaBatchLoaderRegistry.forName()) and the method's parameter name intended for keys are caught at compile or startup time, rather than runtime?- Bean-based DataLoaders: Is there a recommended way to register DataLoaders as Spring beans, similar to DGS's
@DgsDataLoaderannotation, for easier management and auto-registration?
Any guidance on these points for a smoother migration would be appreciated.
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.