State changed as code fixing the issue is committed

State changed as build #3045 is successful

Hi and thank you for the instant handling time, as always!

Trying to checking the fixing commit I see that you did enable case insensitive queries but not multiple terms (two words), correct?

Multi term query is supported for fuzzy query. For instance if you query for "onedev server", it will be converted to path pattern **/*onedev*/**/*server*/** automatically. For explicit path criteria query ('Path' is '...'), you should use wildcard chars for missing segments though.

Ok so, thanks to your hint I’ve figured out how to perform “ordered” multi term searches using the *, I’m going to write it here for the convenience of all users:

For instance, this query: https://code.onedev.io/projects?query=canno+project (canno project with the space) doesn’t produce any match

but this query: https://code.onedev.io/projects?query=canno*project (canno*project with the explicit * wildcard instead of space) does the job

I say “ordered” because the wildcard workaround isn’t a full replacement for “& search operator” therefore order of search terms matters, then in our example https://code.onedev.io/projects?query=project*canno doesn’t produce the match

the search experience isn’t the best, but now that it’s case-insensitive is more than acceptable

thank you so much!

Thanks for the suggestion. Will make this improvement in next patch release.

State changed as code fixing the issue is committed

State changed as build #3052 is successful

… and now we have a top-notch search :)

I can confirm everything works as expected, thank you Robin!

Thank you for all the suggestion. Really appreciated!