mirror of
https://github.com/storytold/designcraft.git
synced 2026-10-27 11:46:51 -06:00
a50d279cba
* test(datamerge): pin facing-page record placement (#198) #198 reported that with `facingPages: true` the merged records after the first landed at identical coordinates on one spread, leaving a later page empty. That no longer reproduces: `data.merge` now builds a new document rather than duplicating pages inside the template, and the three records land on absolute pages 0, 1 and 2 with no overlap. Nothing in the engine changed here. These two tests pin the behaviour the issue asked for, both at the one-record-per-page plan and at the short block that tiles, so a future refactor of `tile_records` can't quietly bring the stacking back. Refs #198 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com> * Merge origin/main; the facing-pages merge tests find each frame's page with page_of_item Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Codebuff <noreply@codebuff.com> Co-authored-by: Brandon Thomas <echelon@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>