[Feature Request]: Improve Delete Rows UX for Clarity and Transparency

[croblesm]

Feature Description

The Delete Rows feature in the View & Edit Data grid currently removes rows immediately from the grid and then requires the user to click Save Changes to commit.

While this works functionally, the current UX provides no visual indication of which rows are pending deletion, nor visibility into the SQL that will be executed.

Current Behavior

• Selecting Delete row immediately removes rows from the grid.
• Aside from the toast notification, there is no visual feedback in the grid showing which rows are pending deletion.
• The pending changes panel updates, but the link between the grid state and pending operations is unclear.
• Undoing deletions requires closing the data grid webview.

Proposed Improvements

• Keep deleted rows visible in the grid but visually marked as pending deletion (e.g., red background, strikethrough text, or “Marked for deletion” label).
• Add a clear undo option for individual deletions without requiring users to close the grid or discard all pending changes.
• Ensure the pending changes panel visually synchronizes with the grid, reflecting the same deletion state.
• Maintain the existing Apply and Discard Changes workflow — this enhancement focuses solely on improving clarity and transparency during row deletion.

cc @yoleichen, @jdesai-24

Screen.Recording.2025-11-07.at.6.44.35.PM.mov

Problem and Motivation

Currently, deleting rows is a silent operation that removes data from the grid without clearly indicating what will be affected on commit.
This leads to user confusion and uncertainty about which records were deleted and which SQL commands will run.

Improving the UX will:

• Make delete operations clear, traceable, and reversible.
• Reduce accidental deletions and increase user confidence.
• Create a transparent and safe workflow consistent with modern data-editing patterns.

Related Area

• Connection dialog (SQL Server | Azure browse/Fabric browse)
• Query results panel
• Query editor
• Object Explorer
• Table Designer
• Schema Compare
• Schema Designer
• Local SQL Server Container provisioning
• SQL database in Fabric provisioning
• GitHub Copilot integration
• Query Plan Visualizer
• Other (please describe below)

If you selected "Other", please describe the area

Edit data

Confirmation

• I have searched existing feature requests and couldn't find a match
• I want to help implement this feature