fix(site-finder): склеить разорванный regex в _PLANNING_NO_MATCH_SQL (#1230) #1270

Merged

bot-backend merged 1 commit from fix/krt-lookup-regex-broken-newline-recovered into main

2026-06-13 07:51:34 +00:00

bot-backend commented

2026-06-13 07:43:31 +00:00

Collaborator

Closes #1230

bot-backend added 1 commit 2026-06-13 07:43:32 +00:00

fix(site-finder): склеить разорванный regex в _PLANNING_NO_MATCH_SQL (#1230 )

Deploy / build-frontend (push) Blocked by required conditions

Details

Deploy / deploy (push) Blocked by required conditions

Details

Deploy / changes (push) Successful in 7s

Details

Deploy / build-backend (push) Has been cancelled

Details

Deploy / build-worker (push) Has been cancelled

Details

CI / changes (pull_request) Successful in 7s

Details

CI / changes (push) Successful in 8s

Details

CI / backend-tests (pull_request) Has been skipped

Details

CI / frontend-tests (pull_request) Has been skipped

Details

CI / backend-tests (push) Has been skipped

Details

CI / frontend-tests (push) Has been skipped

Details

0c62d0b0c3

Литерал regex был разорван переносом строки внутри одной пары '...':
ветки 'Донбасской\\n' и 'Лумумбы\\n' содержали NL+8 пробелов
и никогда не матчили однострочные planning_projects.full_name (PG ~ —
POSIX ARE без (?x)). Geom-only КРТ-fallback молча терял ППТ по этим двум
топонимам.

Patch: вынес паттерн в _KRT_TOPONYM_REGEX через Python adjacent-literal
concat, склеил в SQL через +. Все 17 веток в одной строке.
9 krt_lookup тестов зелёные.

Closes #1230