Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Improve fix-all progress bar experience #73412

Merged
merged 1 commit into from
May 10, 2024

Conversation

CyrusNajmabadi
Copy link
Member

FixALlProgressSmall.mp4

@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner May 9, 2024 20:38
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels May 9, 2024
if (value.ClearValue)
{
Interlocked.Exchange(ref _totalItems, 0);
Interlocked.Exchange(ref _completedItems, 0);
Copy link
Member Author

Choose a reason for hiding this comment

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

whoops. we just lost this in a prior refactoring in this space.

@@ -1466,6 +1467,7 @@ internal virtual bool TryApplyChanges(Solution newSolution, IProgress<CodeAnalys

foreach (var projectChanges in projectChangesList)
{
progressTracker.Report(CodeAnalysisProgress.Description(string.Format(WorkspacesResources.Applying_changes_to_0, projectChanges.NewProject.Name)));
Copy link
Member Author

Choose a reason for hiding this comment

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

now, when we're doing the actual application of hte changes to the workspace, you now see progress for that as well.

@@ -165,6 +165,7 @@ private async Task InvokeWorkerAsync(IProgress<CodeAnalysisProgress> progressTra
// Clear the progress we showed while computing the action.
// We'll now show progress as we apply the action.
progressTracker.Report(CodeAnalysisProgress.Clear());
progressTracker.Report(CodeAnalysisProgress.Description(EditorFeaturesResources.Applying_changes));
Copy link
Member Author

Choose a reason for hiding this comment

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

Now, after cleanup, and selecting "apply" we actually "Applying changes" :)

So user sees 3 passes.

First: Gettins the initial fixes.
Second: Cleaning them.
Third: Applying them to workspace.

@@ -11,6 +11,7 @@
using System.Threading;
using System.Threading.Tasks;
using Microsoft.CodeAnalysis;
using Microsoft.CodeAnalysis.CodeActions;
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: needed?

Copy link
Contributor

@ToddGrun ToddGrun left a comment

Choose a reason for hiding this comment

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

:shipit:

@CyrusNajmabadi CyrusNajmabadi merged commit fc36883 into dotnet:main May 10, 2024
25 checks passed
@CyrusNajmabadi CyrusNajmabadi deleted the fixALlProgress branch May 10, 2024 00:01
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone May 10, 2024
@Cosifne Cosifne modified the milestones: Next, 17.11 P2 May 28, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants