Mavis
aebee77843
Built the missing piece that connects the ksp-bridge to a real KSP instance via kRPC. This adds a typed service client on top of the existing KRPCClient, plus the SpaceCenter-specific extraction logic that pulls the universe state from a running KSP save. @kerbal-rt/krpc-client - types.ts — runtime representation of kRPC Type descriptors (TypeCode enum, KrpcType interface, decodeKrpcType, typeName) - decoder.ts — kRPC value codec: primitive decode/encode, class refs, enums, collections (LIST/SET/TUPLE/DICTIONARY), system messages (STATUS/SERVICES/STREAM/EVENT/PROCEDURE_CALL). 34 unit tests. - services.ts — ServiceCache built from KRPC.GetServices() response. Lookup by (service, procedure), enum value/name resolution. 12 tests. - service-client.ts — KrpcServices: high-level invoke-by-name client. loadServices() helper to connect + load catalog. 9 integration tests with a mock kRPC server. - schema.ts — added Set/Dictionary/Event/Expression types so the decoder can handle system messages without external .proto files. Also fixed a bug where 'STREAM' was being encoded as 0 due to protobufjs's nested-enum string lookup. ksp-bridge - extract.ts — the actual SpaceCenter calls. ~280 procedure calls per poll for a typical KSP save (UT, bodies, vessels, then per-body and per-vessel class methods in parallel). Build the UniverseSnapshot. - krpc-adapter.ts — rewrote to use KrpcServices (typed) instead of the stub extract function. Supports an optional injected services for testing. - bridge.ts — uses the new ExtractedState type and buildSnapshot. - index.ts — connects to kRPC; falls back to mock mode if no server. - convert.ts — backward-compat shim, re-exports from extract.ts. The ksp-bridge can now talk to a real KSP install. We do NOT need the kRPC mod's .proto files on disk — the server's GetServices() response is the source of truth for type info. Documented the full list of procedures we call, the kRPC value encoding, and the new architecture in ksp/README.md. Tests: 119 total, all green. Typecheck and build clean across all 11 projects. Bonus: fixed an integer-overflow bug in the krpc-client connect() handshake (was passing 'RPC'/'STREAM' strings to protobufjs; its nested-enum string lookup silently encodes as 0, which made the stream handshake send the wrong type. Switched to numeric codes.)
45 lines
1.3 KiB
TypeScript
45 lines
1.3 KiB
TypeScript
/**
|
|
* convert.ts — backward-compatibility shim.
|
|
*
|
|
* The real conversion code lives in ./extract.ts. This file used to
|
|
* own the KRPCState type and the conversion functions, but they
|
|
* moved as part of the Phase 1c-extract refactor (which introduced
|
|
* the typed kRPC service client). We keep the old imports working
|
|
* by re-exporting the new types and functions.
|
|
*
|
|
* New code should import from ./extract.ts directly.
|
|
*/
|
|
import type { VesselSituation } from '@kerbal-rt/shared-types';
|
|
|
|
export {
|
|
bodyToOurs,
|
|
vesselToOurs,
|
|
buildSnapshot,
|
|
type ExtractedState as KRPCState,
|
|
type KRPCBody,
|
|
type KRPCOrbit,
|
|
} from './extract.js';
|
|
|
|
// Re-export the situation mapper. The new extract.ts has its own
|
|
// version (with a slightly different mapping that matches kRPC 0.5.x
|
|
// exactly). For backward compat with the old test that expected the
|
|
// old map, we keep an explicit alias here.
|
|
|
|
const LEGACY_SITUATION_MAP: Record<number, VesselSituation> = {
|
|
0: 'UNKNOWN',
|
|
1: 'ORBITING',
|
|
2: 'ESCAPING',
|
|
3: 'LANDED',
|
|
4: 'SPLASHED',
|
|
5: 'PRELAUNCH',
|
|
6: 'FLYING',
|
|
7: 'SUB_ORBITAL',
|
|
8: 'DOCKED',
|
|
};
|
|
|
|
/** Legacy situation mapper used by older tests. Prefer the one in
|
|
* extract.ts for new code. */
|
|
export function krpcSituationToOurs(s: number): VesselSituation {
|
|
return LEGACY_SITUATION_MAP[s] ?? 'UNKNOWN';
|
|
}
|