opencrabs 0.5.0

//! #764 R1: shared option validation mechanics (`check_options`). The
//! tool-specific error wording is pinned by each tool's own tests; these
//! pin the shared trim/filter/min/max/dedup behavior itself.

use crate::channels::question_common::{OptionsError, check_options};

#[test]
fn trims_and_drops_empties() {
    let out = check_options(
        vec!["  a ".into(), "".into(), "   ".into(), "b".into()],
        1,
        8,
    )
    .expect("two valid options");
    assert_eq!(out, vec!["a", "b"]);
}

#[test]
fn too_few_reports_counts() {
    assert_eq!(
        check_options(vec!["only".into(), "".into()], 2, 8),
        Err(OptionsError::TooFew { got: 1, min: 2 })
    );
}

#[test]
fn too_many_reports_count() {
    let raw: Vec<String> = (0..9).map(|i| i.to_string()).collect();
    assert_eq!(check_options(raw, 1, 8), Err(OptionsError::TooMany(9)));
}

#[test]
fn duplicate_rejected() {
    assert_eq!(
        check_options(vec!["x".into(), " x".into()], 1, 8),
        Err(OptionsError::Duplicate("x".into()))
    );
}

#[test]
fn distinct_options_pass() {
    assert_eq!(
        check_options(vec!["x".into(), "y".into()], 2, 8).expect("distinct pair"),
        vec!["x", "y"]
    );
}

// ── #1176 G1/G3: per-channel budgets + the single char-based truncator ──────

#[test]
fn truncate_label_passthrough_under_budget() {
    let out = crate::channels::question_common::truncate_label("short", 10);
    assert_eq!(out, "short");
}

#[test]
fn truncate_label_exact_budget_is_passthrough() {
    let s = "exact!";
    let out = crate::channels::question_common::truncate_label(s, s.chars().count());
    assert_eq!(out, s);
}

#[test]
fn truncate_label_cuts_on_char_boundaries_with_ellipsis() {
    // multibyte probe: budget 5 -> cut 2 CHARS + "..." — never splits a glyph
    // (the byte-based truncate_str this replaces would have panicked here).
    let out = crate::channels::question_common::truncate_label("héllo🎉world", 5);
    assert!(out.starts_with("hé"));
    assert!(out.ends_with("..."));
    assert!(out.chars().count() <= 5);
}

#[test]
fn truncate_label_reproduces_the_historic_fold_shape() {
    // over-budget label -> (budget-3) chars + "...", exactly the old
    // take(57)+"..." contract at budget 60. Telegram no longer uses a budget
    // (#1204 gave it a layout ladder instead), but the helper still backs
    // Discord and Slack and this is the shape they rely on.
    let long = "x".repeat(100);
    let out = crate::channels::question_common::truncate_label(&long, 60);
    assert_eq!(out.chars().count(), 60);
    assert!(out.ends_with("..."));
}

#[test]
fn channel_budgets_stay_sane() {
    use crate::channels::question_common::{DISCORD_LABEL_BUDGET, SLACK_LABEL_BUDGET};
    use crate::channels::telegram::suggest_options::MAX_BUTTON_CHARS;
    // Evaluated at compile time: these are consts, so a runtime assert both
    // trips `assertions_on_constants` and defers to run-time a contradiction
    // the compiler can already see.
    const {
        assert!(DISCORD_LABEL_BUDGET > 0 && SLACK_LABEL_BUDGET > 0);
        // Telegram's ladder replaced its budget: past this width a label
        // cannot ride a button at all and becomes a numbered entry, so no
        // Telegram label is ever silently cut (#1204).
        assert!(MAX_BUTTON_CHARS > 0);
    }
}