Skip to content

fix: pass site as the cached search-index context (render-once D7)#307

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

fix: pass site as the cached search-index context (render-once D7)#307
markdumay merged 1 commit into
mainfrom
fix/render-once-d7-diagnostics

Conversation

@markdumay

Copy link
Copy Markdown
Contributor

Render-once program — slice D7

Both GetSearchIndex partialCached calls now pass site as context (the partial depends only on site.Home; language key kept). Byte-neutral, verified additionally with lazyLoad forced on.

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

GetSearchIndex derives the index URL from site.Home only, so key the
partialCached call on site and its language instead of the global page
context. No output change; removes a misleading page-context dependency
(render-once design, slice D7 / design section 4.5).

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

Copy link
Copy Markdown
Contributor Author

🎉 This PR is included in version 5.0.3 🎉

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