Generate Documentation - incorrect buffer bug

[akhera99]

ApplyDocumentationEditsAsync is invoked with textView.TextBuffer, but the edit spans are based on the snapshot passed in (captured from the subject buffer in the command handler). In projection scenarios these buffers can differ, and translating spans across snapshots from different buffers will fail. Use the buffer associated with the captured snapshot when applying edits.

Microsoft Reviewers: Open in CodeFlow

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Fixes a buffer-mismatch bug in the Copilot “Generate Documentation” flow by ensuring documentation edits are applied to the same ITextBuffer that the captured ITextSnapshot came from, avoiding span translation failures in projection-buffer scenarios.

Changes:

• Remove the ITextView parameter from GenerateAndApplyDocumentationAsync since it’s no longer needed for applying edits.
• Apply generated documentation edits using snapshot.TextBuffer instead of textView.TextBuffer to keep span translation within the same buffer.

Show a summary per file

File	Description
src/EditorFeatures/Core/DocumentationComments/CopilotGenerateDocumentationCommentManager.cs	Applies documentation edits to the snapshot’s buffer to prevent cross-buffer span translation failures (notably in projection scenarios).

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1