Files
galaxy-game/pkg/schema/fbs/battle.fbs
T
Ilia Denisov ebd156ece2
Tests · UI / test (push) Has been cancelled
Tests · Go / test (pull_request) Successful in 2m6s
Tests · Go / test (push) Successful in 2m7s
Tests · Integration / integration (pull_request) Successful in 1m47s
Tests · UI / test (pull_request) Failing after 3m42s
battle-fetch: migrate to user.games.battle ConnectRPC command
The Phase 27 BattleViewer was the last UI surface still issuing raw
fetch() against the backend REST contract (`/api/v1/user/games/...
/battles/...`). The dev-deploy gateway never proxied that path, so
the viewer worked only in tools/local-dev/. Move it onto the signed
ConnectRPC channel every other authenticated surface already uses.

Wire pieces:
- FBS GameBattleRequest in pkg/schema/fbs/battle.fbs, regenerated
  Go + TS bindings.
- MessageTypeUserGamesBattle constant + GameBattleRequest struct in
  pkg/model/report/messages.go.
- pkg/transcoder/battle.go gains GameBattleRequestToPayload and
  PayloadToGameBattleRequest helpers.
- gateway games_commands.go switches on the new message type and
  GETs /api/v1/user/games/{id}/battles/{turn}/{battle_id}; the JSON
  response is re-encoded as a FlatBuffers BattleReport before being
  returned. 404 from backend surfaces as the canonical `not_found`
  gateway error.
- ui/frontend/src/api/battle-fetch.ts now builds the FBS request,
  calls GalaxyClient.executeCommand, and decodes the FBS response
  into the existing UI shape (Record<string,string> race/ship maps,
  string-form UUID). BattleFetchError carries an HTTP-style status
  derived from the result code so the active-view's not_found branch
  keeps working.
- battle.svelte pulls the GalaxyClient from the in-game shell
  context. While the layout's boot Promise.all is in flight the
  effect stays in `loading` until the client handle becomes
  non-null.
- ui/Makefile FBS_INPUTS gains battle.fbs.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-16 12:41:54 +02:00

63 lines
1.1 KiB
Plaintext

// report reflects model/report/BattleReport data object
namespace battle;
struct UUID {
hi:uint64;
lo:uint64;
}
table RaceEntry {
key:int64;
value:UUID (required);
}
table TechEntry {
key:string;
value:float32;
}
table BattleReportGroup {
in_battle:bool;
number:uint64;
number_left:uint64;
load_quantity:float32;
tech:[TechEntry];
race:string;
class_name:string;
load_type:string;
}
table ShipEntry {
key:int64;
value:BattleReportGroup;
}
table BattleActionReport {
attacker:int64;
attacker_ship_class:int64;
defender:int64;
defender_ship_class:int64;
destroyed:bool;
}
table BattleReport {
id:UUID (required);
planet:uint64;
planet_name:string;
races:[RaceEntry];
ships:[ShipEntry];
protocol:[BattleActionReport];
}
// GameBattleRequest is the signed-gRPC request payload for
// `MessageTypeUserGamesBattle`. Gateway forwards this into the
// backend's `GET /api/v1/user/games/{game_id}/battles/{turn}/{battle_id}`
// endpoint after resolving the caller's runtime player mapping.
table GameBattleRequest {
game_id:UUID (required);
turn:uint32;
battle_id:UUID (required);
}
root_type BattleReport;