Add search syntax for operators and phrases #11411
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gargron
force-pushed
the
feature-search-syntax
branch
from
1ffd5af
to
777ee83
Compare
ykzts
approved these changes
Jul 27, 2019
hiyuki2578
pushed a commit
to ProjectMyosotis/mastodon
that referenced
this pull request
Oct 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Supports syntax like:
+foo(AND) and-bar(NOT)"hello world"foo:"hello world"(currently unused)It does change the default of treating all words as joined by AND, so "quick fox" will include items that only contain "fox" and only contain "quick" as well (although items containing "quick fox" will score higher, like before).
The new phrase syntax allows to search for an exact sequence of words instead.
Included is also a small change that allows circumventing the URL resolving logic to use only the search even when a URL is given, when the
resolveparam is set to false. I believe that's how it should have been all along.