commando 1.1.0

An interactive CLI tool to help you write conventional commit messages with ease.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

use crate::input::interactive::InteractiveError;
/// Footer section — breaking change description, issue refs, co-authors.
///
/// Breaking change here is the source of truth. The '!' marker in the
/// header is derived automatically by CommitMessage when
/// breaking_change.is_some() — we never ask about it separately.
use crate::ports::ui::Ui;

pub fn collect_breaking_change<U: Ui>(ui: &U) -> Result<Option<String>, InteractiveError> {
    let is_breaking = ui
        .confirm("5. Does this break existing functionality?")
        .map_err(InteractiveError::Ui)?;

    if !is_breaking {
        ui.println("");
        return Ok(None);
    }

    ui.println("");
    ui.println("Describe what breaks and how users should adapt:");
    ui.println("");

    loop {
        let input = ui
            .prompt("Breaking change: ")
            .map_err(InteractiveError::Ui)?;

        if input.is_empty() {
            ui.println("  ✗ Description cannot be empty. Press Ctrl+C to abort.");
            continue;
        }

        ui.println("");
        return Ok(Some(input));
    }
}

pub fn collect_refs<U: Ui>(ui: &U) -> Result<Option<String>, InteractiveError> {
    ui.println("6. Issue references (optional — press Enter to skip):");
    ui.println("   e.g. #123, closes #456");
    ui.println("");

    let input = ui.prompt("Refs: ").map_err(InteractiveError::Ui)?;

    ui.println("");

    if input.is_empty() {
        Ok(None)
    } else {
        Ok(Some(input))
    }
}