Ilia Denisov
004aca4e97
CI / changes (pull_request) Successful in 3s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 15s
CI / ui (pull_request) Successful in 55s
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m20s
The account time zone defaults to UTC until a player saves a profile, so a report's Filed time could only render in UTC even for a player clearly in another zone. Capture the client's detected "±HH:MM" offset (browser_tz) with each submission and show the Filed time in three zones in the operator console — UTC, the browser offset detected at submit, and the sender's saved profile zone — each shown "N/A" when not known, so the operator can tell what is certainly known from what is merely defaulted. - Thread browser_tz through the fbs envelope (+ Go/TS codegen), the gateway transcode + backend client, and the backend feedback service/store; add the column via migration 00004 (additive, image-rollback-safe). - Fix fmtTimeIn to resolve "±HH:MM" offsets via account.ResolveZone; time.LoadLocation alone silently fell back to UTC for offset zones, which is the second reason a "+02:00" sender showed only UTC. - Update ARCHITECTURE/FUNCTIONAL(+ru) docs and the feedback integration test.
12 lines
606 B
SQL
12 lines
606 B
SQL
-- Capture the client's detected UTC offset ("±HH:MM") with each feedback message, so the
|
|
-- operator console can show the filed time in the sender's browser-local zone even before that
|
|
-- player has ever saved a profile (the account zone defaults to UTC until then). Nullable, so the
|
|
-- rows that predate this keep working — additive and backward-compatible, so a backend image
|
|
-- rollback stays DB-safe (older code simply ignores the column).
|
|
|
|
-- +goose Up
|
|
ALTER TABLE backend.feedback_messages ADD COLUMN browser_tz text;
|
|
|
|
-- +goose Down
|
|
ALTER TABLE backend.feedback_messages DROP COLUMN browser_tz;
|