If you are talking about the following reference then, it was done because this class is created before all services are created.

At that moment, IUriIdentityService was not available. I just checked and it seems IUriIdentityService is now available in startup. So will adopt it.

I think I can also replace following

with

This is what I have found on top (basically reference search on FileSystemProviderCapabilities.PathCaseSensitive)

• vscode/src/vs/platform/extensionManagement/node/extensionsWatcher.ts

  Line 42 in ee1655a

  const extUri = new ExtUri(resource => !fileService.hasCapability(resource, FileSystemProviderCapabilities.PathCaseSensitive));

• vscode/src/vs/platform/userDataSync/common/abstractSynchronizer.ts

  Line 132 in bda864b

  this.extUri = this.fileService.hasCapability(environmentService.userDataSyncHome, FileSystemProviderCapabilities.PathCaseSensitive) ? extUri : extUriIgnorePathCase;

• vscode/src/vs/platform/userDataSync/common/abstractSynchronizer.ts

  Line 837 in bda864b

  this.extUri = this.fileService.hasCapability(environmentService.userDataSyncHome, FileSystemProviderCapabilities.PathCaseSensitive) ? extUri : extUriIgnorePathCase;

All of the above are in platform namespace and run in shared process but IUriIdentityService is a workbench service and not available in platform. I would be happy to adopt it if we have this service available for shared process.

The only thing the UriIdentityService needs is the file service so it should be easy to add that to the shared process

👍 should be easy to add anywhere the file service is there, even main process.

Cool, then will add it in shared process.

• Moved IUriIdentityService to platform
• Registered this in Shared process, CLI, remote
• Used IUriIdentityService#extUri at above mentioned places except in fileUserDataProvider because the service is not available during then.