From 8039a8b4fb4d36c9dcb9ef3a62a5cbffcdae1df6 Mon Sep 17 00:00:00 2001 From: altair823 Date: Mon, 4 May 2026 16:39:23 +0000 Subject: [PATCH] review(p9-fb-24-task1): allow(dead_code) on PAGE_STEP until Task 2 consumes it Co-Authored-By: Claude Opus 4.7 (1M context) --- crates/kebab-tui/src/pager.rs | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/crates/kebab-tui/src/pager.rs b/crates/kebab-tui/src/pager.rs index bdeabb1..7781f58 100644 --- a/crates/kebab-tui/src/pager.rs +++ b/crates/kebab-tui/src/pager.rs @@ -8,4 +8,10 @@ //! lives behind this single edit point. /// Rows scrolled per `PgUp` / `PgDn` keystroke. +/// +/// `#[allow(dead_code)]` is intentional for the Task 1 commit only — +/// Task 2 (Inspect refactor) immediately consumes the constant and +/// removes this attribute. Without it, `cargo clippy -- -D warnings` +/// rejects this commit alone, breaking the per-task review gate. +#[allow(dead_code)] pub(crate) const PAGE_STEP: u16 = 10;