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

Fix updating committed solution with insignificant changes #77648

Merged
merged 3 commits into from
Mar 21, 2025

Conversation

tmat
Copy link
Member

@tmat tmat commented Mar 18, 2025

When a change doesn't produce an update (e.g. a comment is changed) we need to update the last committed solution, otherwise we will see this change again the next time.

When a document content can't be read due to IO error or the document being out of sync, block applying the change and report an error (instead of warning). The user can try to re-apply the edit if that happens.

@tmat tmat requested a review from a team as a code owner March 18, 2025 00:54
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead labels Mar 18, 2025
@tmat
Copy link
Member Author

tmat commented Mar 20, 2025

@davidwengier ptal

@tmat tmat merged commit 38f239f into dotnet:main Mar 21, 2025
25 checks passed
@tmat tmat deleted the EncInsignificantChanges branch March 21, 2025 14:32
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead VSCode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants