Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cancel the current request #82

Open
d3w3r opened this issue Oct 17, 2024 · 4 comments
Open

Cancel the current request #82

d3w3r opened this issue Oct 17, 2024 · 4 comments
Labels
Bug Report that something does not work properly.
Milestone

Comments

@d3w3r
Copy link

d3w3r commented Oct 17, 2024

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:

image

The solution could be a cancel button for the request.

@d3w3r
Copy link
Author

d3w3r commented Oct 17, 2024

Trying this argument in the url was a bad idea 😆

image

@danirod
Copy link
Owner

danirod commented Oct 17, 2024

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)

@danirod danirod added the Bug Report that something does not work properly. label Oct 17, 2024
@danirod danirod added this to Cartero Oct 17, 2024
@danirod danirod moved this to To Do in Cartero Oct 17, 2024
@danirod danirod added this to the 0.2 milestone Oct 17, 2024
@d3w3r
Copy link
Author

d3w3r commented Oct 17, 2024

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.

@danirod
Copy link
Owner

danirod commented Oct 22, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report that something does not work properly.
Projects
Status: To Do
Development

No branches or pull requests

2 participants