feat(core): per-revision spec reference types and the 2026-07-28 wire contract surface (#2252)
This commit is contained in:
parent
ab552c30d5
commit
8d55531dab
1 changed files with 4146 additions and 1005 deletions
|
|
@ -75,7 +75,7 @@ When verifying spec compliance, consult the spec directly rather than relying on
|
|||
|
||||
### Schema Compliance
|
||||
|
||||
- When editing Zod protocol schemas in `schemas.ts`, verify unknown-key handling matches the spec `schema.ts`: if the spec type has no `additionalProperties: false`, the SDK schema must use `z.looseObject()` / `.catchall(z.unknown())` rather than implicit strict — over-strict Zod (incl. `z.literal('object')` on `type`) rejects spec-valid payloads from other SDKs. Also confirm `spec.types.test.ts` still passes bidirectionally. (#1768, #1849, #1169)
|
||||
- When editing Zod protocol schemas in `schemas.ts`, verify unknown-key handling matches the spec `schema.ts`: if the spec type has no `additionalProperties: false`, the SDK schema must use `z.looseObject()` / `.catchall(z.unknown())` rather than implicit strict — over-strict Zod (incl. `z.literal('object')` on `type`) rejects spec-valid payloads from other SDKs. Also confirm the `spec.types.*.test.ts` comparisons still pass bidirectionally. (#1768, #1849, #1169)
|
||||
|
||||
### Async / Lifecycle
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue