Problem

When viewing a diff of a newly added image file, the application throws an error instead of properly displaying the image on one side and an empty side on the other.

This issue occurs because the EMPTY_FILE_SCHEME was using a TextDocumentContentProvider, which is designed only for text documents. When VS Code attempts to render a diff with a binary file (such as an image) on one side and an empty file on the other, the text-based provider cannot handle the binary content, resulting in an error.

Solution

Replaced the TextDocumentContentProvider with a proper FileSystemProvider implementation that supports both text and binary files:

• Created EmptyFileSystemProvider - A new class implementing the vscode.FileSystemProvider interface
• Binary-safe content handling - The readFile() method returns Uint8Array(0) (an empty binary buffer), which works for both text and binary files
• Updated provider registration - Changed from registerTextDocumentContentProvider to registerFileSystemProvider

Technical Details

The key difference is:

• TextDocumentContentProvider.provideTextDocumentContent() returns a string - only suitable for text
• FileSystemProvider.readFile() returns Uint8Array - works for both text and binary content

When a file is added (status = FileChangeStatus.Added), the code in changes/files.ts sets baseFileUri = emptyFileUri. With this fix, the empty file is now properly handled by the new EmptyFileSystemProvider, enabling correct diff display for newly added images.

Changes

• Modified extensions/github1s/src/providers/index.ts:
  • Added EmptyFileSystemProvider class implementing FileSystemProvider
  • Replaced text-based provider registration with file system provider
  • Added /empty path to emptyFileUri for proper file system handling

Fixes the issue described in: "当有新增图片时，在diff视图报错" (Error in diff view when there are new images)

Fixes #13

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.