Skip to content

codelessly_sdk 7.0.1: build the canvas from the resolved node registry - #60

Merged
rayliverified merged 1 commit into
masterfrom
claude/hopeful-brown-c8o8x7
Oct 13, 2026
Merged

rayliverified merged 1 commit into
masterfrom
claude/hopeful-brown-c8o8x7

Conversation

@rayliverified

Copy link
Copy Markdown
Contributor

Summary

On web release builds, every published layout loaded by slug (e.g. on CodelesslySite) failed with Exception: Node with id not found and rendered the grey error screen. Debug builds were fine.

Cause: CodelesslyLayoutBuilder resolves parent links in loadLayout and stores the nodes in nodeRegistry. The layout can then be replaced by a freshly decoded copy with the same lastUpdated, which didUpdateWidget deliberately does not reload. The canvasNode getter read from widget.layout, so the canvas came from that copy, whose nodes have no parent links. PassiveRectangleWidget then called getNode('').

Fix: canvasNode reads the canvas from nodeRegistry (the resolved node) and falls back to widget.layout only when it isn't registered. No state is reset.

Version bumped to 7.0.1 with a changelog entry.

Test plan

  • flutter analyze lib: no issues; flutter test: 34 passed.
  • Reproduced on a CodelesslySite release web build against prod with four published slugs (5stars, Apex, 2911warriors, 0bgmlki1muer): all failed on 7.0.0, all render with this change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01A67XoQYsLVvoMtiKcXXUxY


Generated by Claude Code

On web release builds every published layout failed with "Node with id
 not found": the layout was replaced by a freshly decoded copy with the
same lastUpdated, didUpdateWidget did not reload it, and the canvas was
built from that copy, whose nodes have no parent links. Read the canvas
from the node registry, which loadLayout resolved.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A67XoQYsLVvoMtiKcXXUxY
@rayliverified
rayliverified merged commit e18c963 into master Oct 13, 2026
2 checks passed
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.

2 participants