Skip starting a separate task for backup and restore operations #25285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When performing backup & restore operations from the new admin dialogs, two tasks were being started in the tasks pane. This is because STS starts its own task in the background when doing the restore operation, in addition to the one that always gets started when clicking OK in an admin dialog. This change skips starting a background task on OK if the dialog is a backup or restore one. I refactored the submit logic for the dialogs so that they start a background task in the Dialog
onClosed
callback, rather than registering a background task up front ininitialize
that then gets started after closing. Subclass dialogs then extend thehandleDialogClosed
callback method registered foronClosed
to add more functionality.Fixes #25105