You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, funny thing. Not all cases are covered in tests and there is a bug with one of these.
Here is an example of test with or condition:
// test/unit/helper_spec.jsit('when (true, false) and resolver throws, it should return exactly that error',()=>{constresolver=or(successResolver,failureResolver);consttestError=newError('test');constfinalResolver=resolver(()=>{throwtestError;});returnfinalResolver().catch(err=>{expect(err).to.equal(testError);});});
So, if first resolver succeed it immediately runs query. But if query throws, second resolver runs after that and if it is throws, we receive that second error, but not the error that query throws
The text was updated successfully, but these errors were encountered:
Hi, funny thing. Not all cases are covered in tests and there is a bug with one of these.
Here is an example of test with
or
condition:So, if first resolver succeed it immediately runs query. But if query throws, second resolver runs after that and if it is throws, we receive that second error, but not the error that query throws
The text was updated successfully, but these errors were encountered: