feat: FederatedTypePromiseResolver to settle all promises regardless of errors #1753
+223
−28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
the
FederatedTypePromiseResolver
was originally created with theDataLoader
use case in mind, meaning that all returnedCompletableFuture
s are resolved synchronously, to letDataLoader
dispatch mechanism to decide when to dispatch, so realistically, when usingDataLoader
s, there is not an scenario where a particularCompletableFuture
might complete exceptionally.However, nothing stops users to use the
FederatedTypePromiseResolver
without dataloaders, which means that nowCompletableFuture
s might complete exceptionally in a asynchronous way.To solve that, create allSettled extension function
which will complete all promises even if one or more complete exceptionally. The type of each element in the returned list will be a kotlin Result that encapsulates a successful outcome with a value of type
T
or a failure with the exception.🔗 Related Issues
#1747