Add an option to allow the user to change the full-text search behavior in the Contents admin UI.

[MikeAlhayek]

Fix #13886

[jtkech]

I did another review

LGTM but maybe worth to be able to also define the default operator, hmm as I remember we also needed to define a full quoted string because when searching for pete seeger the customer only want results containing the whole, no result like pete foo played music with albert seeger.

But I'm not against if we agree that it could be done in separate PRs.

[MikeAlhayek]

I did another review

LGTM but maybe worth to be able to also define the default operator, hmm as I remember we also needed to define a full quoted string because when searching for pete seeger the customer only want results containing the whole, no result like pete foo played music with albert seeger.

But I'm not against if we agree that it could be done in separate PRs.

made some more changes and added double-quotes. Let me know if you see anything else.

[jtkech]

Okay, let @sebastienros decide which options are worth to support, maybe also the default operation, and the Full Quoted String as a separate option with an higher precedence. Yes I think that if we support the Quoted String it should be an option.

Maybe the options would need to be able to return a full DefaultTermNode.

In my case I was checking if there is no explicit operator in use, maybe we don't need this, just take into account the current options, but not sure, would need to focus on it more.

[MikeAlhayek]

@jtkech I added UseQuotationMarks option which is false by default so we don't change existing behavior. Currently, the user can achieve this by wrapping the string with double-quotes themself. This is better I think because the user has full control. The user should only turn on this option if they really need to always use double quote.

[jtkech]

Currently, the user can achieve this by wrapping the string with double-quotes

Does it work? As I remember it was not working when I tried it, but not sure now

I don't like the UseQuotationMarks option name, maybe AsQuotedString

[MikeAlhayek]

@jtkech I renamed UseQuotationMarks to UseExactMatch. I cleaned up the doc blocks and cleaned up the code. I also tested with and without UseExactMatch and it is working as expected. By default UseExactMatch is set to false so we do not change the default behavior of Orchard.

[MikeAlhayek]

@jtkech let me know if you see anything need changes or approve it please.

[jtkech]

Okay, I will look at it this night, I may do some last minor changes and then approve (or merge).

[jtkech]

Okay, I did some last changes and approved, I let you review my changes