You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that there is a small complication in that it doesn't make sense to provide the --exact at the top-level, because the user may want to run a batch with both KEYWORD_EXACT_PHRASE and KEYWORD_UNORDERED queries. The current implementation allows this by treating any line that starts and ends with a quotation mark (") as an exact query, and any other line as not exact (even if it contains quotation marks in other positions).
Note that the behavior of the search API doesn't seem to exactly match the documentation. I just confirmed that it's possible to run searches for an exact phrase (via quotation marks here, which get translated into KEYWORD_EXACT_PHRASE) and get results that don't contain that phrase, either in the search result or the complete library page. This is the case even if you ignore punctuation in the result.
As a hypothetical example, if your query line is "foo bar ai", you may get some results that include the string "foo bar ai", but also some with just "Foo Bar - AI", or even without any version of that phrase at all. If you omit the quotation marks, you will get different results, and you likely won't even see the "Foo Bar - AI" items.
As a side note, I don't see any way to search for "foo bar" ai, interpreted as the exact phrase "foo bar" AND the term "ai", since KEYWORD_EXACT_PHRASE vs. KEYWORD_UNORDERED is specified per-query. Given that the documentation doesn't match reality, though, there might be some way to do this that isn't described there.
This file contains hidden or 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
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.
Fixes #2.
Note that there is a small complication in that it doesn't make sense to provide the
--exactat the top-level, because the user may want to run a batch with bothKEYWORD_EXACT_PHRASEandKEYWORD_UNORDEREDqueries. The current implementation allows this by treating any line that starts and ends with a quotation mark (") as an exact query, and any other line as not exact (even if it contains quotation marks in other positions).