Deferred by design decision 2026-09-01, split from the #28 export work.
Cascade export produces a zip of HTML files with inter-note links rewritten to sibling files. The PDF counterpart cannot use that shape: links between separate PDF files are handled inconsistently across viewers and break when files move, so per-file cascade PDF is rejected outright.
The one respectable form is a single merged PDF: concatenate the cascaded notes into one HTML document and turn note links into internal anchors, so links become page jumps inside one file. Precondition to verify before building anything: whether Chromium's printToPDF preserves anchor links in the produced PDF. The base printToPDF path itself is confirmed working in a real vault via electron.remote.
Until then: PDF export stays per note, cascade stays HTML only. Nothing in the current export architecture blocks adding this later.
Deferred by design decision 2026-09-01, split from the #28 export work.
Cascade export produces a zip of HTML files with inter-note links rewritten to sibling files. The PDF counterpart cannot use that shape: links between separate PDF files are handled inconsistently across viewers and break when files move, so per-file cascade PDF is rejected outright.
The one respectable form is a single merged PDF: concatenate the cascaded notes into one HTML document and turn note links into internal anchors, so links become page jumps inside one file. Precondition to verify before building anything: whether Chromium's printToPDF preserves anchor links in the produced PDF. The base printToPDF path itself is confirmed working in a real vault via electron.remote.
Until then: PDF export stays per note, cascade stays HTML only. Nothing in the current export architecture blocks adding this later.