Skip to content

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

Merged
merged 1 commit into from
Aug 28, 2019

Conversation

lucasrcosta
Copy link
Contributor

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.

@lucasrcosta lucasrcosta force-pushed the use-response-executor branch 3 times, most recently from 8036719 to 1b89362 Compare September 20, 2018 21:14
@lucasrcosta
Copy link
Contributor Author

lucasrcosta commented Jan 30, 2019

@syrusakbary no interest on this?

Copy link

@dan98765 dan98765 left a 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?

@lucasrcosta
Copy link
Contributor Author

Will do @dan98765! o>

@Cito Cito force-pushed the master branch 2 times, most recently from d21bdd4 to c781f01 Compare May 4, 2019 16:37
@lucasrcosta lucasrcosta force-pushed the use-response-executor branch 3 times, most recently from 7251d70 to 96f5a0d Compare May 16, 2019 23:12
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.
@lucasrcosta lucasrcosta force-pushed the use-response-executor branch from 96f5a0d to 786849b Compare May 17, 2019 19:01
@lucasrcosta
Copy link
Contributor Author

@dan98765 is this test enough?

@lucasrcosta
Copy link
Contributor Author

lucasrcosta commented Jun 24, 2019

No one to give this a thought?

@msdinit
Copy link

msdinit commented Aug 22, 2019

@dan98765 @syrusakbary Is there anything else preventing this from being merged?

Copy link
Contributor

@ekampf ekampf left a 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.

@ekampf
Copy link
Contributor

ekampf commented Aug 28, 2019

@dan98765 can you approve your change requests? this looks good to merge to me

@ekampf ekampf merged commit 7ff9553 into graphql-python:master Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants