[#RSRP-33312] "Safe Delete": Proposed Change in Workflow — First Check for Conflicts, then Ask for Confirmation

ReSharper

"Safe Delete": Proposed Change in Workflow — First Check for Conflicts, then Ask for Confirmation

Created: 12 Dec 06 19:12 Updated: 12 May 08 19:39

Component/s:

Refactorings - Safe Delete

Fix Version/s:

Future Versions

Security Level:

Everybody (All jira users)

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Issue Links:

Duplicate

This issue is duplicated by:
	~~RSRP-40390~~ Safe delete should show dependent dec...

Fixed in build:

400

Description

« Hide

Goal: less user actions in case there're conflicts.

Current behavior:

If there are no conflicts, then the safe-delete-confirmation is displayed and then the deletion is performed. OK and, basically, nothing to improve.
If there are conflicts, then the user first sees the safe-delete-confirmation dialog, then the safe-delete-conflicts dialog. The former is unneded because the latter is just as good a confirmation. The first dialog is unnecessary and just annoys a bit.

Proposed behavior:
First, check for conflicts with a standard progress UI. Then:

If there are no conflicts, display the safe-delete-confirmation that should clearly state that there are NO conflicts, already checked for that.
If there are conflicts, display the safe-delete-conflicts dialog and so on.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Andrey Simanovsky - 27 Dec 06 18:40

Checking for conflicts is a potentially long operation - a progress needs to be shown.

[ Permlink | « Hide ]

Ilya Ryzhenkov - 04 Sep 07 13:29

Currently, it even worth. It displays useless first page of workflow, then it searches for conflicts, and either silently delete or show conflicts. Should be as follows:

User invokes Safe Delete
Workflow popups and immediately starts to search for conflicts
If conflicts are found, they are displayed
If there are no conflicts, page with clear state about no conflicts should be shown as confirmation
If there are auto-resolvable conflicts (like safe-deleting empty interface), they should be presented with some sort of "green mark"