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 @josnidhin the culprit are these lines. As you see there the behavior is intentional. It is replicating Request's original behavior in case no callback is registered. The reason is that the error you reported in particular is thrown before the .then(...) method is called. So at that point in time the code cannot differentiate between:
rq('test');rq('test').then(...).catch(...);
By nature we have a situation here that allows no perfect solution in all cases. However, it could be the case that I can find a different solution that provides a better compromise. It will take me some time to work on, though.
Expects the code to log 'failed' on console but instead throws error
The text was updated successfully, but these errors were encountered: