You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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 viaBatchLoaderRegistry.forName()
) and the method's parameter name intended for keys are caught at compile or startup time, rather than runtime?@DgsDataLoader
annotation, for easier management and auto-registration?Any guidance on these points for a smoother migration would be appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: