Clarify request value limits for inline schemas
This commit is contained in:
@@ -128,9 +128,12 @@ or tests coupled to incidental copier call counts.
|
||||
|
||||
## 3. P3 — Scope The Existing Request-Value Limit Documentation
|
||||
|
||||
Status: open. Identified by the follow-up integration audit. Relevant stages:
|
||||
Status: complete. Identified by the follow-up integration audit. Relevant stages:
|
||||
1, 6, and 8.
|
||||
|
||||
Resolution: RunRequest GoDoc now scopes bounded copying to Execution.ExtraParams
|
||||
and explicitly distinguishes inline schema documents. No runtime limits changed.
|
||||
|
||||
`types.go:82–86` still says generically that excessively deep or large
|
||||
JSON-shaped request values are rejected. The new `OutputContract.Schema` route
|
||||
deliberately uses standard JSON encoding/decoding and trusted document copying,
|
||||
|
||||
Reference in New Issue
Block a user