undefined xhr and response objects on last catch #113
Comments
Are you catching the good error argument as expected? |
What do you mean? |
In the last |
Error is equal to the string "400 (Bad Request)" |
Which one? xD |
The |
You gave me two different errors, which one is the error parameter? :p |
Of I've erased the first error on the comments because it was a mistake, there is a one error only. |
Ah! My bad, I should have refresh the page ;) So the good error is catched, it's just the arguments that are not valid. I'll look that tomorrow! |
Thanks! |
I think this is not a bug but the internal behavior of PinkySwear, the library that qwest uses for its promises layer. Since an error is thrown in a |
Then, I think I can't deal with this issue because I can't see a way to deal with the PinkySwear's internal routines. Can't you use the grouped requests as described in the documentation? |
I'm closing this for idling ;) |
Hello,
I chain queries as follows. The last one returns an error 400 with a JSON object in response that provides detailed information. This response should be available in the last catch but it is undefined, as well as the xhr object:
Tested using v4.1.1
The text was updated successfully, but these errors were encountered: