{"version":"2.1.227","anchor":"layout-caching-moved-onto-the-nodes-themselves","canonical_anchor":"layout-caching-moved-onto-the-nodes-themselves","heading":"Layout caching moved onto the nodes themselves","tier":"internal","area":"Terminal Rendering","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/layout-caching-moved-onto-the-nodes-themselves","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Layout caching moved onto the nodes themselves\n\nLayout data moved onto each node, and mixing layout configurations now raises an error.\n\n**What**\n\nCached layout rectangles and pending-clear tracking now live on each layout node rather than in a side lookup table, and the counters for nodes visited, measure calls and cache hits moved onto the layout configuration object. Adding a child created under a different configuration now raises an error instead of producing inconsistent layout.\n\n**Evidence**\n\n`insertChild: child was created with a different Config`\n\n- Area: Terminal Rendering\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}