Skip to content

Rename renderNode → intercept; useFormTree({ defaults }) (#142) - #148

Merged
timkindberg merged 1 commit into
mainfrom
feat/142-rename-intercept-defaults
Aug 14, 2026
Merged

Rename renderNode → intercept; useFormTree({ defaults }) (#142)#148
timkindberg merged 1 commit into
mainfrom
feat/142-rename-intercept-defaults

Conversation

@timkindberg

Copy link
Copy Markdown
Owner

Summary

Closes #142 (child of #141).

Customize had two jobs under one name. This ships the ADR 051 split: defaults is the table <Default /> draws, intercept is this node.

  • renderNodeintercept on SchemaFields / <Default /> / vanilla
  • defaultAdapternativeDefaults, diagnosticAdapterdiagnosticDefaults, plus mergeDefaults on the renderer packages
  • useFormTree(tree, { defaults }) binds createRenderer(mergeDefaults(nativeDefaults, defaults))
  • Core keeps RendererAdapter / mergeAdapter
  • Team composition is a userland useTeamFormTree wrapper, not a library context

No intercept-map sugar (#143) and no gallery rewrite (#146). Examples just got the rename so they compile.

Agent did the grind.

Test plan

  • useFormTree({ defaults }) merges over native, not diagnostic (unspecified slots stay real HTML)
  • intercept still hijacks a node when defaults are bound
  • Core still exports mergeAdapter / RendererAdapter
  • CI green

…#142)

Ship ADR 051 teaching names on React and vanilla. Kind-wide look binds via
defaults; intercept stays the per-node SchemaFields prop. Core engine types
are unchanged.

Co-authored-by: Cursor <cursoragent@cursor.com>
@timkindberg
timkindberg merged commit 7f25622 into main Aug 14, 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.

Rename renderNode → intercept; useFormTree({ defaults })

1 participant