Skip to content

fix: optimize the renderer by using child map in virtual dom - #81

Open
bchelkowski wants to merge 2 commits into
masterfrom
fix--optimize-the-renderer-by-using-child-map-in-virtual-dom
Open

bchelkowski wants to merge 2 commits into
masterfrom
fix--optimize-the-renderer-by-using-child-map-in-virtual-dom

Conversation

@bchelkowski

Copy link
Copy Markdown
Member

No description provided.

@bchelkowski
bchelkowski requested a review from a team as a code owner July 17, 2026 13:25
@bchelkowski
bchelkowski requested review from kamil-dazn and saikiranreddydavu and removed request for a team July 17, 2026 13:25
- store the normalised virtual DOM before componentDidMount so a synchronous
  forceUpdate() from there no longer re-renders the whole tree
- mark children maps with an explicit __childrenMap/byId structure instead of
  detecting them by a missing name field, so child ids like 'name' or 'count'
  cannot break collection detection or shadow AA methods
- assign dense order values (skipping Invalid and dropped children) so
  insertChild indexes are not shifted by conditionally hidden children
- recurse into children when marking id-less elements for removal, so switching
  the render output shape no longer leaks the previous subtree
- warn about children with missing or duplicated props.id instead of silently
  dropping them; duplicated ids keep the position of the first occurrence
- expose normaliseVNode as a public KopytkoDiffUtility method
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant