Add a non-whitespace pattern to SearchQueriesParam.

[wRAR]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.14%. Comparing base (37fcbee) to head (ac59dc3).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #74   +/-   ##
=======================================
  Coverage   97.14%   97.14%           
=======================================
  Files          16       16           
  Lines         946      946           
=======================================
  Hits          919      919           
  Misses         27       27           

Files with missing lines	Coverage Δ
zyte_spider_templates/spiders/serp.py	85.18% <ø> (ø)

[Gallaecio]

Wouldn’t this prevent multi-word queries, like searching for “foo bar”?

[wRAR]

Hmm, apparently it tries to match the entire value even without ^$

[Gallaecio]

When defining the regular expressions, it's important to note that the string is considered valid if the expression matches anywhere within the string.
https://json-schema.org/understanding-json-schema/reference/string#regexp

So, I’m thinking this should do the trick:

Suggested change

	"pattern": r"(.|\r?\n)*\S+(.|\r?\n)*",
	"pattern": r"(.|\r?\n)*?\S",

Or maybe even (your original?):

Suggested change

	"pattern": r"(.|\r?\n)*\S+(.|\r?\n)*",
	"pattern": r"\S",

[wRAR]

Well, the initial one didn't work on a multi-word input (neither does r"\S") so I don't know if the quote is true. Or maybe the frontend code uses it incorrectly.

[Gallaecio]

Or maybe the frontend code uses it incorrectly.

Oh, right, the frontend is most likely not using some JSON schema library, and instead uses its own implementation, which might be assuming an initial ^ (like Python’s re.match vs re.search).