support search for literals for repository code search with indexer

[darren]

Feature Description

Sometimes searching for SQL/function in code results in bad hits. eg: search swaggerParameterBodies in my local mirror of gitea:

which is actually defined in

gitea/routers/api/v1/swagger/options.go

Line 16 in d88b012

type swaggerParameterBodies struct {

not showing in the first page of the search result.

this is the indexer config

[indexer]
REPO_INDEXER_ENABLED = true
REPO_INDEXER_PATH = indexers/repos.bleve
# # 300k
MAX_FILE_SIZE = 307200
REPO_INDEXER_INCLUDE = 
REPO_INDEXER_EXCLUDE = go.sum,package-lock.json

Support searching for literals by enclosing search terms in double quotation marks would be better.

For bleve using Match Phrase Query

Screenshots

No response

[darren]

The case I tested above is swaggerParameterBodies, but I searched a local repo with a lot SQL queries and I am not quite satisfied with the search results thus I filed this issue.

As with the swaggerParameterBodies above I assume even using MatchQuery /routers/api/v1/swagger/options.go should come first, why?

[jpraet]

More in general, I think your example screenshot above illustrates a problem I also notice on my instance after upgrading from 1.22 to 1.23.

Why is a search on "swaggerParameterBodies" returning results for "swagger"? Is that intended? Possible related to #32261?

Edit: not related to #32261, but instead to #32210: it changed the bleve query from NewMatchPhraseQuery to NewMatchQuery.