Skip to content
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

Add "Accept All" / "Reject All" Buttons to Resolutions View #105

Open
ibolton336 opened this issue Nov 19, 2024 · 0 comments
Open

Add "Accept All" / "Reject All" Buttons to Resolutions View #105

ibolton336 opened this issue Nov 19, 2024 · 0 comments

Comments

@ibolton336
Copy link
Member

We need to enhance the Resolutions View in our Visual Studio Code extension by adding "Accept All" and "Reject All" buttons. This will allow users to quickly accept or reject all suggested changes at once, improving the workflow efficiency when dealing with multiple resolutions.

Details
The Resolutions View currently requires users to manually accept or reject each change. This can be time-consuming and cumbersome, especially when there are multiple changes suggested. By implementing an "Accept All" and "Reject All" functionality, we can streamline the process, significantly reducing the time users spend on this task.

Technical Implementation
Webview Page Updates:

Modify the ResolutionPage component to include "Accept All" and "Reject All" buttons.

These buttons should only be enabled when there are changes to accept or reject.
On click, these buttons should trigger a function that sends a batch message to the VS Code backend using the existing sendVscodeMessage utility.

Update the setupWebviewMessageListener function to handle new messages for batch actions:
applyAllChanges: This should trigger the application of all pending changes.
revertAllChanges: This should discard all suggested changes.

Ensure that these actions update the extension's state correctly and provide feedback to the user through notifications.

State Management and UI Feedback:

Manage state to track changes that have been applied or reverted.

Update the UI to reflect the state after batch actions are completed, possibly refreshing the view or displaying a summary of actions taken.

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

No branches or pull requests

1 participant