dev_agentandClaude Opus 5.5
267d0be4a6
CI / ci (push) Successful in 8m11s
Recipe extraction no longer falls back to the URL's host: a stored recipes.site_name is now always a name the page gave (publisher or og:site_name), and null when it named none. dinners.SourceOf is the one documented rule for every fetched recipe's source: the page's name is shown as it stands; otherwise the site is named by the link's host only when the link itself is shown as free of secrets, else null. The recipe detail, idea results and the recipe-candidate offer endpoint all apply it; candidates no longer carry an extraction-time hostname fallback, so their site_name is nullable (frontend updated to match). Migration 0020 clears host-shaped site names (dotted host names, IP addresses) stored before the change, in recipes and in legacy idea job results, so already-stored rows read under the same rule. Maestro 966066e3-0e25-4b8b-9bb0-0694c47c9106 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
37 lines
1.8 KiB
SQL
37 lines
1.8 KiB
SQL
-- 0020_site_name_from_page: recipes.site_name now holds only the name a
|
|
-- recipe page gives its site (its publisher's name or og:site_name), and is
|
|
-- null when the page names none; a client is credited with the link's host
|
|
-- only when dinners.SourceOf finds the link safe to show. Before this, a
|
|
-- page naming no site was stored under the host of the URL it was served
|
|
-- from, which may carry a personal token, and nothing recorded which a
|
|
-- stored name was. A stored name that could be a host — a dotted host name
|
|
-- or an IP address, spelled only in host characters — is cleared here, so
|
|
-- every stored name is one a page gave. A site that names itself as a
|
|
-- domain, such as "Food.com", loses its stored name with them until its
|
|
-- recipe is fetched again, and is credited by its link's host meanwhile
|
|
-- when the link is safe.
|
|
--
|
|
-- Idea job results stored before sources were made safe hold the grounded
|
|
-- recipe's site name as it was stored, and are cleared the same way: an
|
|
-- idea's stored site name is shown as it stands. The ideas array is
|
|
-- rebuilt from a plain scan of json_each, which yields its elements in
|
|
-- array order, so the ideas keep their order (sqlc's parser refuses an
|
|
-- ORDER BY inside json_group_array).
|
|
|
|
UPDATE recipes SET site_name = NULL
|
|
WHERE site_name GLOB '*[.:]*' AND site_name NOT GLOB '*[^-A-Za-z0-9.:]*';
|
|
|
|
UPDATE jobs SET result = json_set(result, '$.ideas', (
|
|
SELECT json_group_array(
|
|
CASE
|
|
WHEN json_extract(idea.value, '$.site_name') GLOB '*[.:]*'
|
|
AND json_extract(idea.value, '$.site_name') NOT GLOB '*[^-A-Za-z0-9.:]*'
|
|
THEN json_set(idea.value, '$.site_name', json('null'))
|
|
ELSE json(idea.value)
|
|
END
|
|
)
|
|
FROM json_each(jobs.result, '$.ideas') AS idea
|
|
))
|
|
WHERE kind IN ('ideas_from_ingredients', 'quick_ideas')
|
|
AND json_type(result, '$.ideas') = 'array';
|