Ilia Denisov
e9f836db87
Tests · Go / test (push) Successful in 9s
Tests · Integration / integration (push) Successful in 10s
Tests · UI / test (push) Successful in 20s
Tests · Go / test (pull_request) Successful in 8s
Tests · Integration / integration (pull_request) Successful in 11s
Tests · UI / test (pull_request) Successful in 19s
Service-agnostic refinement of the owner's idea: the sign-in service returns a set of supported game languages with the user identity, and the lobby gates the New Game variant choice by it (en -> English; ru -> Russian + Эрудит). - Connector hosts two bots in one container (one per service language, each its own token + game channel; the same telegram_id spans both). ValidateInitData tries each token and returns the validating bot's service_language + supported_languages. Per-language config (TELEGRAM_BOT_TOKEN_EN/_RU, channels). - supported_languages rides the Session (fbs, session-scoped, not persisted); the UI offers only the matching variants on New Game — gating only the START of a new game (auto-match + friend invite), not accept/open/play; backend does not enforce. - service_language persisted (accounts.service_language, migration 00010, written every login, last-login-wins) and routes the user-facing Notify push back through the right bot (push-target coalesces with preferred_language). - Admin SendToUser/SendToGameChannel gain an operator-chosen language selector in the console (unrelated to ValidateInitData). - Non-Telegram logins carry the gateway default set (GATEWAY_DEFAULT_SUPPORTED_LANGUAGES, all variants). Wire (committed regen): ValidateInitDataResponse +service_language +supported_languages; Session +supported_languages; SendToUser/SendToGameChannel +language. Docs (ARCHITECTURE/FUNCTIONAL/_ru/READMEs) + PLAN updated; stage marked done.
22 lines
925 B
SQL
22 lines
925 B
SQL
-- +goose Up
|
|
-- Stage 15 dual Telegram bots: service_language records the language tag of the bot
|
|
-- a Telegram user last authenticated through (their last ValidateInitData). It is
|
|
-- updated on every Telegram login — new and existing accounts — and routes the
|
|
-- user's out-of-app push back through the right bot. It is distinct from
|
|
-- preferred_language (the interface language) and from a game's variant language.
|
|
-- Nullable: an account that has never signed in through a tagged bot (legacy,
|
|
-- email-only or guest) has no value, and push routing falls back to
|
|
-- preferred_language. Adds a column, so the generated jet code is regenerated
|
|
-- (cmd/jetgen).
|
|
SET search_path = backend, pg_catalog;
|
|
|
|
ALTER TABLE accounts
|
|
ADD COLUMN service_language text
|
|
CHECK (service_language IN ('en', 'ru'));
|
|
|
|
-- +goose Down
|
|
SET search_path = backend, pg_catalog;
|
|
|
|
ALTER TABLE accounts
|
|
DROP COLUMN service_language;
|