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,
|
||||
|
||||
5
types.go
5
types.go
@@ -82,8 +82,9 @@ const (
|
||||
// Prepare, PrepareExecution, and Run copy the request's maps, pointers, and
|
||||
// nested JSON-compatible values before using them. The caller may mutate the
|
||||
// request after any method returns. A successful PrepareExecution retains its
|
||||
// own private execution snapshot for RunPrepared. Excessively deep or large
|
||||
// JSON-shaped values are rejected for safety.
|
||||
// own private execution snapshot for RunPrepared. Execution.ExtraParams uses
|
||||
// bounded JSON-value copying and rejects excessively deep or large values.
|
||||
// Inline JSON Schema documents do not use those provider-extra copy limits.
|
||||
type RunRequest struct {
|
||||
// OperationTimeout selects a whole-operation budget when positive. Run
|
||||
// applies it across preparation and execution; PrepareExecution retains it
|
||||
|
||||
Reference in New Issue
Block a user