fix(vscode): Text duplication when using VSCode git utilities #4338

[denbezrukov]

Summary

Fix #4338

It seems that we are receiving two different DidOpenTextDocument events with different URI schemes. The first one has the scheme "file", which indicates that the file is being accessed directly from the file system. The second one has the scheme "git", which suggests that the file is being accessed from a Git repository. After that we're receiving an change event.

rome_lsp::handlers::text_document::did_open{params=DidOpenTextDocumentParams { text_document: TextDocumentItem { uri: Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/lo.ts", query: None, fragment: None }, language_id: "typescript", version: 1, text: "console.log(\"before\");\n" } }}


│ ├─┐rome_lsp::handlers::text_document::did_open{params=DidOpenTextDocumentParams { text_document: TextDocumentItem { uri: Url { scheme: "git", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/Users/denis.bezrukov/Projects/my-app/src/lo.ts", query: Some(""), fragment: None }, language_id: "typescript", version: 1, text: "console.log(\"before\");\n" } }}

 │ ├─0ms TRACE rome_lsp::handlers::text_document old document: "console.log(\"before\");\n"
│ │ ├─0ms TRACE rome_lsp::handlers::text_document content changes: [TextDocumentContentChangeEvent { range: Some(Range { start: Position { line: 0, character: 15 }, end: Position { line: 0, character: 15 } }), range_length: Some(0), text: "fore" }]
│ │ ├─0ms TRACE rome_lsp::handlers::text_document new document: "console.log(\"beforefore\");\n"

I check how other tools handled their files:

• rust-analyzer
• bash-lsp
• deno

Test Plan

???

Changelog

• The PR requires a changelog line

Documentation

• The PR requires documentation
• I will create a new PR to update the documentation

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	b6640f7
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/6439af1ebebbd40008e7786e

[ematipico]

Looks good to me! A test plan be merging the PR and make a nightly build, for example! Or, doing manual testing.