Skip to main content

Module limits

Module limits 

Source
Expand description

VAPP-103: the input LIMITS (catalog/limits.json, generated as LIMIT_NAMES/LIMIT_VALUES): an agent’s input past one is refused with an issue, never worked on. Mirrors src/limits.ts; the issue messages are byte-identical in every core.

Constants§

MAX_COMPONENTS
Nodes the reducer places in one surface’s tree (template nodes included), and nodes one layout build holds: the reduced tree’s plus every template item’s subtree.
MAX_DEPTH
Nesting levels of the REDUCED tree, after macro expansion (the root = 1): every reduced tree stays inside serde_json’s 128-level recursion limit (2 JSON levels per node). The stack is never the bound: the recursive passes grow it on the heap (crate::roomy/crate::deep; tests/robustness.rs lays a 48-level surface out on a 128 KB thread).
MAX_MESSAGE_BYTES
One server message as UTF-8 JSON.
MAX_POINTER_BYTES
A data pointer’s length in UTF-8 bytes.
MAX_POINTER_SEGMENTS
A data pointer’s token count.
MAX_TEMPLATE_ITEMS
Template items one surface instantiates.
USED_TWICE_ISSUE
An id placed a second time (two parents, or one parent twice).

Functions§

components_issue
depth_issue
limit
A limit by name (maxDepth, maxMessageBytes, …).
message_bytes_issue
template_items_issue