-
Notifications
You must be signed in to change notification settings - Fork 70
Use Executor for getting responses #13
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
Use Executor for getting responses #13
Conversation
8036719
to
1b89362
Compare
@syrusakbary no interest on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(@syrusakbary has been very busy and is transitioning a lot of his graphql-python project maintenance to folks in the community; I'm just an interested volunteer...)
This is a great change! @lucasrcosta how do you feel about adding new/updated tests before it gets merged in?
Will do @dan98765! o> |
d21bdd4
to
c781f01
Compare
7251d70
to
96f5a0d
Compare
Use an Executor of the same type as configured to get backend responses.This leverages the batching functionality, allowing batched requests to be processed concurrently.
96f5a0d
to
786849b
Compare
@dan98765 is this test enough? |
No one to give this a thought? |
@dan98765 @syrusakbary Is there anything else preventing this from being merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
@dan98765 can you approve your change requests? this looks good to merge to me |
Use an Executor of the same type as configured to get backend responses.
This leverages the batching functionality, allowing batched requests to be processed concurrently.