Custom filesystems - stabilization of FileSearchProvider and TextSearchProvider

[GraphR00t]

FileSearchProvider and TextSearchProvider are API proposals that are needed to make virtual filesystems more usable. Both APIs have been created several years ago.

Many extension writers have been regularly (re-)asking for the stabilization of both APIs. Would it be possible to have the two corresponding issues fixed this year ? VSCode is a great code editor, and its extension ecosystem is rich because it exposes many APIs to the extension writers. Thank you !

• Stabilize TextSearchProvider API #59921 (6 years ago)

  • Limitations of Source Archive file systems github/vscode-codeql#500
  • Support "find in files" in an ISFS folder intersystems-community/vscode-objectscript#296
  • [Feature Request] Search should search all files iamhyc/Overleaf-Workshop#60
  • [feature] tracking for ast-grep-search-panel minimum viable product ast-grep/ast-grep-vscode#59
  • Does search / fuzzy search work? SchoofsKelvin/vscode-sshfs#2
  • Cannot Search Across Files in Virtual Filesystem #201964

• Stabilize FileSearchProvider API #73524 (5 years ago)

  • Does search / fuzzy search work? SchoofsKelvin/vscode-sshfs#2

My use case

I am developping an extension that connects to a project server (LSP + custom methods) for development. There are no local files. I implement a FilesystemProvider that communicates with a virtual filesystem present on the project server.

Having FileSearchProvider and TextSearchProvider available (without the users needing to use VSCode Insiders) would greatly improve the UX.

[gjsjohnmurray]

Pinging @andreamah 🙏

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!