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
request.js is not good enough when an exception occurs in response, such as 500. The code still run continuelly when an exception has been caught. request.js return undefined in catch(), which finally resolves the promise chaining.
I think it will be more comfortable to intuition if the promise chaining can be stop when it see an exception.
I have used this resolution in my project for a few months. Everything works fine.
Maybe antd pro also like this feature I think? I'm happy to help with a PR if someone like it.
The text was updated successfully, but these errors were encountered:
request.js
is not good enough when an exception occurs in response, such as 500. The code still run continuelly when an exception has been caught.request.js
return undefined in catch(), which finally resolves the promise chaining.I think it will be more comfortable to intuition if the promise chaining can be stop when it see an exception.
I have used this resolution in my project for a few months. Everything works fine.
Maybe antd pro also like this feature I think? I'm happy to help with a PR if someone like it.
The text was updated successfully, but these errors were encountered: