Skip to content

fix: attribute diagnostic warnings to the intrinsic page (render-once D7)#164

Merged
markdumay merged 1 commit into
mainfrom
fix/render-once-d7-diagnostics
Jul 16, 2026
Merged

fix: attribute diagnostic warnings to the intrinsic page (render-once D7)#164
markdumay merged 1 commit into
mainfrom
fix/render-once-d7-diagnostics

Conversation

@markdumay

Copy link
Copy Markdown
Contributor

Render-once program — slice D7

34 sites switched (23 components via D4's $page, 11 layout partials via their page schema arg); none left global.

Part of the Hinode render-once implementation program (design: gethinode.com docs/superpowers/specs/2026-07-15-content-render-once-design.md §2.3/§4.5/§6-D7, Appendix C). Diagnostics-only: replaces global-page warning attribution with the intrinsic page where one is in scope; no output bytes change.

Gate: exampleSite with all four D7 module branches replaced simultaneously — 0 ERROR, 98/26/24 pages, WARN set identical; candidate vs unpatched-main control: byte-neutral (only the 3 allowlisted RSS files). Independently re-verified by the program driver. Module test suites green.

🤖 Generated with Claude Code

Use the injected _page prop (with global fallback) in the component
warning paths and the threaded page argument in the layout partials. The
global page context identifies the render that triggered the call, which
can be a foreign page when another render materializes this page's
content (render-once design, slice D7).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@markdumay markdumay merged commit d9a8250 into main Jul 16, 2026
8 checks passed
@markdumay

Copy link
Copy Markdown
Contributor Author

🎉 This PR is included in version 2.2.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant