Skip to content

tweak: add cancel button to deploy dev center #1243

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ivanma9
Copy link

@ivanma9 ivanma9 commented Apr 1, 2025

Created a cancel button.
Made it cancel deployments.
Issue #1135

@CLAassistant
Copy link

CLAassistant commented Apr 1, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@KernelDeimos KernelDeimos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution! I just reviewed the code but this is still pending a manual test which I plan to do by end of week.

@@ -1074,101 +1075,7 @@ async function edit_app_section(cur_app_name, tab = 'deploy') {
// Focus on the first input
$('#edit-app-title').focus();

try {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment about why this section of code was removed?

@@ -31,6 +31,9 @@ let dropped_items;
let search_query;
let originalValues = {};

// At the top of your file, add a global variable to track deployment cancellation
let globalDeploymentCancelled = false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can probably just call this deploymentCancelled, since there's no "local deployment" option in the dev center.

@KernelDeimos
Copy link
Contributor

Hello again, please correct me if I'm wrong but - upon manual and further review - cancelling doesn't really do anything, does it? It seems to me it just gives the user the illusion that something is being cancelled but deployment continues as normal. This could still be helpful since it allows the user to start another deployment again quickly if they made a mistake, but that might actually cause issues if there's already a concurrent deployment happening that they don't know about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants