bdeshi/khosra
0
0
Fork 0
Code Issues Pull Requests Releases Activity

make merging the default include model

Browse Source 
Composing a page from several files is why includes exist, and one endnote list
at its end is what that page wants. ADR-0066 kept the old default only so
existing content would not re-render; both models have now been seen and the
human chose. `include: embed` still asks for the other thing.

One-level needed enforcing on the new path: a spliced fragment's own include
line would otherwise be parsed as a call and expanded a second time, which a
test caught. It is dropped during the splice, matching what embed already did.
This commit is contained in:
Claude Opus 5
2026-08-02 00:25:10 +06:00
committed by bdeshi
parent 67defae912
commit aa9bd2a489
8 changed files with 64 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
examples/demo-site/content/writing/notes-on-water/index.en.md
+1 -2
View File
@@ -2,7 +2,6 @@
title: Notes on Water
date: 2026-03-25
tags: [monsoon, journal]
include: merge
---
The finished piece. Below, a part of it lives in a separate file and is included here:
@@ -11,7 +10,7 @@ The finished piece. Below, a part of it lives in a separate file and is included
That fragment starts with an underscore, so the scanner never treats it as a bundle: it has no URL of its own
and appears in no listing. An included file cannot itself include — one level, deliberately.
This bundle declares `include: merge`, so the fragment is spliced in before anything is parsed: its footnote
Fragments are spliced in before anything is parsed: its footnote
is numbered with the page's and both appear in one list at the end, rather than one list per part.
This bundle also has an `extras/` directory, so the theme offers a link to it at the foot of the page.