Skip to content

Change draft deploy pop-up from an informational window to a quick pick#771

Merged
MicroFish91 merged 6 commits intomainfrom
mwf/revision-deploy-step
Oct 14, 2024
Merged

Change draft deploy pop-up from an informational window to a quick pick#771
MicroFish91 merged 6 commits intomainfrom
mwf/revision-deploy-step

Conversation

@MicroFish91
Copy link
Copy Markdown
Contributor

@MicroFish91 MicroFish91 commented Oct 14, 2024

Discussed this with Nathan a while back, and we agreed it would probably be better to use a quick pick instead of a pop-up window after each command. This means the prompt to deploy becomes something we ask at the start rather than something we ask after the draft command finishes.

I'm proposing the process now would be - each draft command should push in the following quick pick step as the last prompt:
new RevisionDraftDeployPromptStep()

Almost no 'new' logic has actually been added here, mostly prompt logic from the old RevisionDraftUpdateBaseStep got moved into the new RevisionDraftDeployPromptStep.

Before (informational window):
image

After (prompt quick pick):
image

To see in action, you can test with this command:
image

Edit: I forgot, I also snuck in a small fix for this...
Fixes #683

@MicroFish91 MicroFish91 marked this pull request as ready for review October 14, 2024 20:20
@MicroFish91 MicroFish91 requested a review from a team as a code owner October 14, 2024 20:20
@MicroFish91 MicroFish91 changed the title Change deploy pop-up from an informational window to a quick pick Change draft deploy pop-up from an informational window to a quick pick Oct 14, 2024
Comment thread package.nls.json
"containerApps.revealResource": "Reveal Resource",
"containerApps.description": "An Azure Container Apps extension for Visual Studio Code.",
"containerApps.enableOutputTimestamps": "Prepends each line displayed in the output channel with a timestamp.",
"containerApps.showDraftCommandDeployPopup": "Show an informational deploy pop-up message whenever a draft command is run.",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

is this enabled by default?

Copy link
Copy Markdown
Contributor Author

@MicroFish91 MicroFish91 Oct 14, 2024

Choose a reason for hiding this comment

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

Yeah, it's true by default

Comment on lines +14 to +17
if (!await settingUtils.getGlobalSetting(showDraftCommandDeployPopupSetting)) {
context.shouldDeployRevisionDraft = false;
return;
}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should you try to move this into shouldPrompt? To do so, you could set this context before running the wizard.

Copy link
Copy Markdown
Contributor Author

@MicroFish91 MicroFish91 Oct 14, 2024

Choose a reason for hiding this comment

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

Yeah, nice, good call

@MicroFish91 MicroFish91 force-pushed the mwf/revision-deploy-step branch from 84dcf1f to 9a84f73 Compare October 14, 2024 20:45
@MicroFish91 MicroFish91 merged commit e326783 into main Oct 14, 2024
@MicroFish91 MicroFish91 deleted the mwf/revision-deploy-step branch October 14, 2024 21:15
@microsoft microsoft locked and limited conversation to collaborators Nov 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

There is an extra step "Select subscription" when deploying changes by clicking "Yes" button from the prompt notification

2 participants