Open xareelee opened 7 years ago
hi @xareelee,
When i tested your issue in the webpackbin, I noticed that the asyncReturnError
was being resolved
rather than rejected
is that expected ?
If i change it to reject
similar to your other error functions you get your expected results http://www.webpackbin.com/V1_lYi5Yf
hi @davidchase ,
This test case is obtained from graphql-js. The error is expected to be resolved
.
I'm trying to replace the Promise-based execute()
with Observable-based (like most.js), and this is the one failed test case.
I try to use Most.js instead of RxJS.
The following code obtains an unexpected result:
I'll get
asyncReturnError
first as unexpected. It seems that the error events from Promise in Most.js are not synchronous.When I use RxJS, I can get the errors in the same sequence as the executors, but not when using Most.js.
How can I fix this if it is not a bug?