This issue relates to the fact that the search bar can only ever display either the normal output (text search) or output from Inkuire. But never both.
This led to some hacks in Inkuire. For example the following declaration:
val xd: String = ???
has to be searched in Inkuire using => String, instead of just String.
This is because the heuristic for choosing which search engine to use is a simple searchPhrase.contains("=>") check.
So the scope of this issue would be to figure out a better way to choose the search engine. Preferably even add Inkuire as a separate section in the search results. Though always using both search engines should IMHO be out of the question, since that would kill the performance of the normal search bar.
This issue relates to the fact that the search bar can only ever display either the normal output (text search) or output from
Inkuire
. But never both. This led to some hacks in Inkuire. For example the following declaration:has to be searched in Inkuire using
=> String
, instead of justString
. This is because the heuristic for choosing which search engine to use is a simplesearchPhrase.contains("=>")
check.So the scope of this issue would be to figure out a better way to choose the search engine. Preferably even add Inkuire as a separate section in the search results. Though always using both search engines should IMHO be out of the question, since that would kill the performance of the normal search bar.