Skip to content

Conversation

samuelAndalon
Copy link
Contributor

📝 Description

originally we decided to have the KotlinDataLoader to allow passing the BatchLoader fn instead of the DataLoader instance because of the new Instrumentation to dispatch a DataLoaderRegistry in a more efficient way, so for that we had to decorate the DataLoader CacheMap before instantiating the DataLoader.

a PR in graphql-java-dataloader was merged to natively support what we where doing to the CacheMap, so we can go back to allow passing a DataLoader

so we can theorically go back to previous KotlinDataLoader implementation.

🔗 Related Issues

#1457

@samuelAndalon samuelAndalon added changes: minor Changes require a minor version module: executions issue affects the executions code labels Jun 11, 2022
@samuelAndalon samuelAndalon changed the title feat: KotlinDataLoader to provide DataLoader [executions] KotlinDataLoader to provide DataLoader Jun 11, 2022
@samuelAndalon samuelAndalon merged commit aacd1ee into ExpediaGroup:master Jun 13, 2022
@samuelAndalon samuelAndalon deleted the feat/kotlin-dataloader branch June 13, 2022 22:59
dariuszkuc pushed a commit to dariuszkuc/graphql-kotlin that referenced this pull request Aug 5, 2022
* feat: KotlinDataLoader to provide DataLoader

* feat: adjust coverage

* feat: schema generator with dataloader as test dependency

* feat: avoid excluding dataloader lib in schema generator

* feat: remove unused version variable

Co-authored-by: samvazquez <[email protected]>
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 module: executions issue affects the executions code
Development

Successfully merging this pull request may close these issues.

2 participants