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
Actually if a make a request that takes so much time the current tab of the request is blocked and there is no way to abort the request, i found this problem calling one API that has a bad implementation so i put some images:
The solution could be a cancel button for the request.
The text was updated successfully, but these errors were encountered:
Yeah, I am aware that the application currently lacks a way to cancel requests. I've suffered this and the only way I got to regain control of the program was to open a new tab and continue working there.
The fact that it's still not possible to set a predictable timeout in Cartero also makes the thing more slow.
I think that the least Cartero could do right now is to offer a button to stop the current request somewhere, either replacing the 'Send' button while a request is in progress, or covering the entire response pane. The first approach is faster to implement, the other approach could open more possibilities (displaying error messages in a pane, without using toasts, which is clunky)
Maybe for a timeout what about a preset value for all request and at the same time that inside each request the user can set manually a different timeout.
That's a really good idea, in fact. Maybe each request (and folder and collection) could have its own variable value to override the global settings or the parent settings.
Actually if a make a request that takes so much time the current tab of the request is blocked and there is no way to abort the request, i found this problem calling one API that has a bad implementation so i put some images:
The text was updated successfully, but these errors were encountered: