Is your feature request related to a problem? Please describe.
Not a bug, more usability. I mash Ctrl+S on a file 10 times, it shouldn't queue up 9 more pushes while the first is running. The state that the files were at for times 2-8 are gone forever so it's equivalent to running push 8 times on the final (same) state of the files.
The end result is that I have an almost constant notification for pushes, and (if I save a file in a broken state then immediately fix it) an error notification to dismiss. I can of course cancel the top one, then wait for the next, cancel it, then wait, then cancel, and etc. But obviously a horrible user experience.
Describe the solution you'd like
Only ever have 1 push queued up. It should be a boolean instead of a queue: "Should I initiate another push after this one finishes?"
Describe alternatives you've considered
There are other plugins that have auto-save features but that's irrelevant; if the recommendation was to use those instead then this feature should simply be removed from the official plugin.
Additional context
This pertains to the push-or-deploy-on-save.enabled setting.
Is your feature request related to a problem? Please describe.
Not a bug, more usability. I mash Ctrl+S on a file 10 times, it shouldn't queue up 9 more pushes while the first is running. The state that the files were at for times 2-8 are gone forever so it's equivalent to running push 8 times on the final (same) state of the files.
The end result is that I have an almost constant notification for pushes, and (if I save a file in a broken state then immediately fix it) an error notification to dismiss. I can of course cancel the top one, then wait for the next, cancel it, then wait, then cancel, and etc. But obviously a horrible user experience.
Describe the solution you'd like
Only ever have 1 push queued up. It should be a boolean instead of a queue: "Should I initiate another push after this one finishes?"
Describe alternatives you've considered
There are other plugins that have auto-save features but that's irrelevant; if the recommendation was to use those instead then this feature should simply be removed from the official plugin.
Additional context
This pertains to the
push-or-deploy-on-save.enabledsetting.