The issue with custom schemes in FileSystemProvider?

[yyx1111]

The FileSystemProvider utilizes a custom scheme, but the language service is unable to perceive the workspace under these circumstances and is limited to single files, which can be somewhat perplexing during the development of extensions. Is there a method to resolve this issue, or are there existing alternative solutions that could address it?

[jrieken]

but the language service is unable to perceive the workspace under these circumstances and is limited to single files

Sorry, I don't really understand what this means

[yyx1111]

For instance, when a FileSystemProvider offers access to folders and numerous files, the "Go to Definition" feature fails to navigate to other files within the FileSystemProvider or to definitions within dependency packages.

[jrieken]

the "Go to Definition" feature fails to navigate to other files within the FileSystemProvider or to definitions within dependency package

That depends on the extension computing go to definition results but is independent of vscode