fix(mobile): capture site/origin text params in bug-report auto-context

SiteScenes passes the tube as origin/name (strings), not UUIDs, so the existing UUID-only auto-context loop dropped them. Reports like 'ingest of this site has been stuck 2 days' (14f3a655) arrived without any site identifier. Add a second loop for known string identity params (origin/name/sitetag/tag/q), length-capped, so per-site/per-performer reports become actionable.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
jtrzupek 2026-06-15 09:35:49 +02:00
parent 8b4783771f
commit 3714afa22f

View file

@ -173,6 +173,16 @@ export function BugReportFAB({ client, appVersion, navRef }: Props) {
extraContext.push(`${key}=${val}`); extraContext.push(`${key}=${val}`);
} }
} }
// Identyfikatory tekstowe (nie-UUID): SiteScenes przekazuje stronę jako
// `origin` (sitetag) + `name` (display), PerformerScenes/TagScenes bywa
// po nazwie. Bez tego zgłoszenie "ingest tej strony stoi" nie mówi której
// (bug-report 14f3a655 2026-06-14). Cap długości, żeby nie wlec listy.
for (const key of ['origin', 'name', 'sitetag', 'tag', 'q']) {
const val = params[key];
if (typeof val === 'string' && val.trim() && !UUID_RE.test(val)) {
extraContext.push(`${key}=${val.trim().slice(0, 64)}`);
}
}
} catch { } catch {
// navRef nie ready — zostawiamy puste, backend i tak przyjmie nullable // navRef nie ready — zostawiamy puste, backend i tak przyjmie nullable
} }