Skip to content

Looking for advice on DGS DataLoader migration #1233

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
cw-juyeonyu opened this issue Jun 4, 2025 · 0 comments
Open

Looking for advice on DGS DataLoader migration #1233

cw-juyeonyu opened this issue Jun 4, 2025 · 0 comments
Labels
status: waiting-for-triage An issue we've not yet triaged

Comments

@cw-juyeonyu
Copy link

Hi Spring GraphQL Team,

We're migrating from Netflix DGS to Spring GraphQL and have questions about DataLoader.

  • @SchemaMapping Argument Resolution Validation: When using a DataLoader within a @SchemaMapping method, how can we ensure mismatches between the DataLoader name (registered via BatchLoaderRegistry.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 @DgsDataLoader annotation, for easier management and auto-registration?

Any guidance on these points for a smoother migration would be appreciated.
Thanks!

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Development

No branches or pull requests

2 participants