Ilia Denisov
74455c7b12
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 9s
CI / integration (pull_request) Successful in 15s
CI / ui (pull_request) Successful in 45s
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m10s
Add a per-game rule chosen on New Game for Russian variants (default off = the
single-word rule; on = standard Scrabble). Off, only the main word along the play
direction is validated and scored; perpendicular cross-words are ignored,
including in robot move generation. The rule rides every create and enqueue
request and joins the matchmaking key, so games and auto-match stay one uniform
path; "Russian-only" is a UI affordance (English always sends standard and shows
no toggle).
- Engine: consume scrabble-solver v1.1.0's PlayOptions{IgnoreCrossWords}, threaded
through engine.Options.MultipleWordsPerTurn -> playOpts() into validate, score
and generate.
- Backend: thread the flag through game CreateParams/Game + store (games column),
lobby InvitationSettings + invitation row, and the matchmaker queue key (variant
+ rule); persisted, so a rebuilt-from-journal game keeps it. Baseline migration
gains multiple_words_per_turn (DB not versioned); jet regenerated.
- Edge: multiple_words_per_turn added to the EnqueueRequest / CreateInvitationRequest
FlatBuffers tables (Go + TS regenerated) and threaded through the gateway.
- UI: a "Multiple words per turn" toggle on New Game, shown for Russian variants
only (auto-match and friend invite), default off; English silently sends standard.
- Tests: backend engine/matchmaker; UI unit (gating) + Playwright e2e (solver
corner-case + GCG fixtures ship in v1.1.0). Docs + PRERELEASE tracker updated.
pkg
Shared wire contracts for the Scrabble platform (module scrabble/pkg),
imported by both backend and gateway. It carries no logic — only the
generated message types and the schemas they come from.
Layout
proto/push/v1/ # backend -> gateway live-event gRPC channel (Push.Subscribe)
# committed generated Go (*.pb.go, *_grpc.pb.go)
fbs/scrabble.fbs # FlatBuffers edge payloads (one `scrabblefb` namespace)
fbs/scrabblefb/ # committed generated Go for the schema
proto/push/v1is the single gRPC server-stream the backend exposes and the gateway subscribes to (Event{user_id, kind, payload, event_id}); thepayloadis an opaque FlatBuffers body the gateway forwards verbatim.proto/telegram/v1is the Telegram connector's RPC contract (includingValidateLoginWidgetfor the web Login Widget sign-in).fbsholds the client↔gateway request/response and event payloads as FlatBuffers tables. The backend encodes the push payloads from these types; the gateway transcodes the rest to and from the backend's JSON; the UI generates TypeScript from the same.fbs.
Generated code
Committed (CI only builds it); regenerate dev-time after editing the schemas:
make -C pkg tools # go install protoc-gen-go + protoc-gen-go-grpc
make -C pkg gen # buf generate (proto) + flatc (fbs)
flatc is pinned to 23.5.26 to match the github.com/google/flatbuffers
Go runtime in go.mod; generating with another version is refused.
Workspace wiring
scrabble/pkg is a bare-path module (no dot), so — like scrabble-solver — it
cannot be fetched as a versioned dependency. go.work carries use ./pkg and
replace scrabble/pkg v0.0.0 => ./pkg; consumers require scrabble/pkg v0.0.0.