Chinesezjc
b462d5fd69
Adapt to two contract changes master introduced: - The generated Remote face now wraps every business result in RemoteResult, folding carrier failures into an ok:false branch instead of rejecting. The controller reads that envelope at its three call sites and maps a carrier failure onto the same settled shape the controls already render; three specs cover the new branch. - Client packages split their tsconfig into host and client halves, and the host aggregate now compiles any test not named *.client.spec.*. Rename this package's specs to the client convention and drop the ../connection project reference, which pointed at a solution file that no longer carries the client sources. Keep master's mount loop with its rollback-on-failure in api-remotes and add messageFeedbackRemote to it.
@deepseek-ai/dsh-type-meta
English | 中文
Compiler-independent declarations shared by business packages, generated TypeRT artifacts, the Host Gateway, and Client API. This package owns the Remote Service base, decorators, explicit binding fallback, merge-extensible protocol maps, invocation descriptors, codecs, and provider contracts; it does not run TypeScript analysis or register a concrete Cordis service.
Remote declarations
@Remotemarks a public instance method for direct invocation on its registered Cordis Service.@RemoteScope(key)marks a method whose receiver is selected from a merge-declared scoped Context kind.GatewayServicebinds the Cordis key passed tosuper(ctx, serviceKey, options?)to the same default wire namespace.bindTypeRTGateway(this, serviceKey, options?)provides the same visible, frozen binding for a Service that cannot inherit fromGatewayService.remoteMethods(service)returns a detached declaration-order snapshot used by the Gateway's SRC fallback.
A Host method opts into cooperative cancellation by declaring signal: AbortSignal as its final parameter. InvocationDescriptor.cancellation records that reserved injection point; the signal never becomes a JSON parameter or lookup field. SRC recognizes the final parameter name, while strict generation also verifies the global AbortSignal type.
Decorator initializers retain markers in a module-private WeakMap keyed by the Service prototype. They do not add constructor symbols, prototype properties, parameter metadata, or runtime reflection fields. A GatewayService exposes the same public readonly typertGateway binding that the explicit helper returns.
TypeRT protocol
Business packages extend TypeRTLookupMap and TypeRTContextMap to associate Host objects or scoped Contexts with their wire identities. Generated artifacts extend TypeRTRemoteMap, TypeRTRemoteScopeMap, and TypeRTRemoteNamespaceMap so Client imports expose only selected Remote methods. InvocationDescriptor is the shared runtime form consumed by the registry, Gateway, and Client Remote.
The Host assembly extends TypeRTRemoteEventSelection with the Host events it forwards to consumers, which narrows the ctx.remote.$on key face; TypeRTForwardableEvent states the shapes a one-way delivery can carry at all, excluding Scope-bound and answered events. TypeRTClientRemote carries both roles of that surface: consumers subscribe through $on, and the Client half owning the host frame sink hands frames over through $dispatch.
Lookup and Context packages own both sides of their contract: declaration merging supplies the static association, while runtime providers register identity resolution with ctx.typert. A lookup or Host Context provider supplies the stable declaration and default resolver, while Host composition may separately configure a synchronous or asynchronous resolver; policy rejections may use TypeRTLookupFailure to carry a failure value owned by the boundary adapter. Strict codecs carry generated schemas; src-json codecs identify the weaker source-launch path.
Model Experience
None, as this protocol package declares application reflection and registers nothing model-facing.
KV Cache effect
No direct effect.
Known Limitations and Deferred Work
- Decorator markers contain only the method name and direct or Context invocation mode. Parameter, result, lookup, and schema reflection require the TypeRT build pipeline.
- Remote decorators accept only public, non-static instance methods with string names. SRC execution cannot represent overloaded, destructured, defaulted, or rest-parameter signatures.