feat: type exceptional draft results
This commit is contained in:
@@ -72,12 +72,12 @@
|
||||
complete OpenRPC document for all 70 registered methods. Request payloads
|
||||
retain useful Pydantic schemas, so OpenRPC is a viable transport input.
|
||||
- Typed-result slices now give `workflow.health`, all artifact, deployment,
|
||||
and run operations, and 26 uniform persisted draft-workspace operations
|
||||
named transport-neutral result schemas: 42 of 70 methods. The remaining 28
|
||||
success results still collapse to generic objects, including exceptional
|
||||
draft compile/save shapes and capability/source/admin operations. Continue
|
||||
introducing operation result DTOs before adopting generated TypeScript
|
||||
contracts.
|
||||
and run operations, every persisted draft-workspace operation, and the
|
||||
capability-bootstrap alias named transport-neutral result schemas: 47 of
|
||||
70 methods. The remaining 23 success results still collapse to generic
|
||||
objects across capability discovery/call, stateless draft patch/validate,
|
||||
source discovery, and source-registry/admin operations. Continue introducing
|
||||
operation result DTOs before adopting generated TypeScript contracts.
|
||||
- The stock `@open-rpc/generator` TypeScript client is not suitable here. It
|
||||
exhausted a 4 GB Node heap on the full contract and emitted invalid dotted
|
||||
class members plus `any` results for a minimal `workflow.health` contract.
|
||||
|
||||
Reference in New Issue
Block a user