EiSiMo 77246d1381 fix(notifications): district filter silently dropped every match ... internal.py's flat-match path fed the raw scraper payload into flat_matches_filter, which has no "district" key. Combined with the match rule "active districts filter + unknown district → reject", this meant any user with a non-empty districts filter stopped receiving match notifications as soon as the 0011 migration ran. Extract the Bezirk once from payload.address before the per-user loop, so all users' filter evaluations see a concrete district. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-23 10:18:04 +02:00
..
__init__.py	refactor: split web/app.py into routers	2026-04-21 19:27:12 +02:00
admin.py	refactor: rename wohnungsdidi → lazyflat	2026-04-23 09:26:12 +02:00
auth.py	refactor: split web/app.py into routers	2026-04-21 19:27:12 +02:00
bewerbungen.py	refactor: rename wohnungsdidi → lazyflat	2026-04-23 09:26:12 +02:00
einstellungen.py	feat(filter): Berlin-Bezirk filter in Einstellungen	2026-04-23 10:05:55 +02:00
internal.py	fix(notifications): district filter silently dropped every match	2026-04-23 10:18:04 +02:00
wohnungen.py	feat(filter): Berlin-Bezirk filter in Einstellungen	2026-04-23 10:05:55 +02:00