Expand description
Route component inventory management for incremental route rendering.
These helpers walk the normal render fragment graph. The request-aware path is
route-aware but state-agnostic: it follows the active route chain for the
current request path, while conservatively traversing if, for, and
attribute-template edges without evaluating runtime state.
Structs§
- Protocol
Index - Pre-computed index for a protocol, caching expensive lookups.
- Route
Chain Entry - A single entry in the matched route chain, one per nesting level.
Functions§
- build_
component_ index - Build a deterministic component-name → bit-index map from the protocol.
- collect_
nested_ route_ params - Walk the fragment graph following matched routes and collect all route parameters from every level of the active route chain.
- collect_
route_ chain - Collect the matched route chain for a request path.
- encode_
inventory - Encode an inventory bitfield as a hex string.
- filter_
needed_ components - Filter components against the client’s inventory bitfield using sequential indices. Zero collisions — each component has a unique bit.
- get_
needed_ components - Walk the protocol fragment graph from
entry_idand return the names of all components the route needs that are NOT in the client’s inventory. - get_
needed_ components_ for_ request - Walk the protocol from the persistent
entry_idand return the component templates needed for the currentrequest_path. - parse_
inventory - Parse a hex-encoded inventory string into bytes.
- render_
action_ response - Produce a JSON response for a POST mutation action.
- render_
component_ templates - Return compiled templates and CSS for specific components by tag name.
- render_
partial - Produce a JSON partial response for client-side navigation.