Let extension be able to get current search options

[ppggff]

Let extension be able to get current search options, such as query string, include/exclude info, ...

[roblourens]

What do you want this for?

[ppggff]

To build extension, such as:

First stage:

• expand/hide "search detail" by situation
  • always expand, always hide
  • expand if default option is changed
  • ...
• show current search option in state bar

Second stage:

• pre-defined search or search option in setting
  • run pre-defined search, then restore last search after
  • set to pre-defined search option
• remember search history with options
  • search in the history, and restore selected search (with option)
  • assign key shortcut to some selected search (with option)

Future (may be not):

• use search panel as input/output, search engine
  • auto rewrite user input
  • auto set option base on user input
  • ...

[roblourens]

I can see the use, but we have a bunch of other search API that has been on the backlog for a long time, and I don't see us getting to this in the near future.

[ranyitz]

@roblourens I'm building an extension that will let the user create search presets. So you could search in specific directories / file extensions etc. The use case for the extension is described in the following issue: #101481

While I can build the extension with the existing APIs, I want to create the following features:

1. Save current search parameters into a preset (this should be a better UX than configuration)
2. Preserve the current query when replacing the search preset (include/exclude etc...)

For that, I need to be able to read the current search parameters. I want vscode API to expose a function to get these search parameters

I'll appreciate it if you'll reconsider the decision, and I'm willing to contribute if it helps.