-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Ditching async #93
Comments
#92 might solve your problems. |
Is this still an issue? If so, can you provide a clear description of what you're trying to accomplish and what exact errors you run into? |
trevor-scheer
pushed a commit
that referenced
this issue
May 6, 2020
trevor-scheer
pushed a commit
that referenced
this issue
May 14, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Guys, in all your examples you advocate using async with queries on server. Concerning that node 6.x can now run vanilla es2015 it is the only thing that requires transpilation. I tried not to use async call but I was running through poopstorm of problems with fibers and all. What would be a recommended strategy without asyns/await? Would you care to provide functioning example of e.g. a resolver or mutation without async call, for example based on Promises? I tried several startegies and none seems to work.
The text was updated successfully, but these errors were encountered: