review: the spread test expects the labels in the order they are drawn (CodeRabbit/a spread with a section inside lists its names apart)

Moving page 4 into spread 1 does not move the section that starts at page 3, so the label takes the comma-separated branch: pages 2, 3 and 4 are numbered 2, 1 and 2, and the assertion now expects exactly that. The test failed before this change (left: "2, 1, 2", right: "2-4").
This commit is contained in:
Madhav Agarwal committed 2026-11-16 21:09:45 +05:30
1 parent 1f75a8d8f0
commit 105a080c03
1 file changed
+4 -2
+4 -2
View File
@@ -1317,7 +1317,7 @@ mod spread_label_tests {
/// Bound right to left, a spread's label follows the document's reading order: the left
/// page first ("3–2", not "2–3"), and a section inside a spread lists its pages left to
/// right. Left-to-right labels are unchanged. A spread of more pages, drawn in document
/// order, keeps its label in that order.
/// order, lists its names in that order, apart while a section still starts inside it.
#[test]
fn rtl_binding_labels_spreads_in_visual_left_to_right_order() {
let mut app = app();
@@ -1329,7 +1329,9 @@ mod spread_label_tests {
assert_eq!(got[1], "1, 2");
assert_eq!(got[2], "3–2");
app.run("layout.pages.toSpread", json!({"page": 4, "spread": 1})).unwrap();
assert_eq!(labels(&app)[1], "2–4");
// Three pages, drawn in document order: 2, 3 and 4 are numbered 2, 1 and 2, and the
// section that starts on page 3 stays inside the spread, so the names stay apart.
assert_eq!(labels(&app)[1], "2, 1, 2");
}
/// Labels navigate to document spreads, including when parent editing was active.