-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find in files using extenstion API #9049
Comments
cc @jrieken |
Hi @jrieken, |
That hasn't been exposed yet - mainly because we might change the search engine we use behind the covers which might lead to API breakage... |
Hi @jrieken, |
@roblourens Are we in a good enough state to expose our find in files functionalities for extension authors? Especially wrt regex-searching will we make more changes or is this future proof? |
Yeah, I think we could do this. Someone could implement something like #23931 |
Yeah, like my alternative reference ui: https://github.com/Microsoft/vscode-extension-samples/blob/master/contentprovider-sample/README.md |
Could this be used to create an extension allowing for full page results? This editor is so awesome, but the current find results showing in the sidebar is difficult to use in my opinion. I'd like to make an extension for executing a search and opening the results in an editor (similar to Atom search flow). Excited to see this land! |
Ideally, the search API should match SearchProvider API. Though, instead of registering a new search provider, the goal here is to be able to call it and get the search results. And that should work with the default provider that VSCode implements, when nobody else has actually registered one. |
@jrieken when do you think it can land into VSCode? |
Hi VS code team,
I would like to make an extenstion using
Find in FIles
API.Is there any way to trigger
Find in Files
via extension ?I only find
workspace.findFiles
.Thanks in advance.
The text was updated successfully, but these errors were encountered: