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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
//! # CLI Configuration
//!
//! This module defines the **command-line interface (CLI)** for `leadforge`
//! using [`clap`].
//!
//! It is responsible for:
//!
//! - parsing user input
//! - validating arguments
//! - providing help/usage information
//! - converting CLI commands into domain-level commands
//!
//! ---
//!
//! ## Design Overview
//!
//! The CLI layer is intentionally kept **separate from the core logic**.
//!
//! ```text
//! CLI (clap)
//! ↓
//! Config / Command
//! ↓
//! Conversion (From<Command>)
//! ↓
//! LeadForgeCommand (domain)
//! ↓
//! run()
//! ```
//!
//! This separation ensures:
//!
//! - the core logic is reusable (e.g. in APIs or background jobs)
//! - the CLI remains a thin interface layer
//! - input validation happens at the boundary
//!
//! ---
//!
//! ## Commands
//!
//! Currently supported:
//!
//! - `hacker-news` (alias: `hn`) → fetch job postings from Hacker News
//!
//! Example:
//!
//! ```bash
//! leadforge hacker-news --limit 10 --keyword rust
//! ```
//!
//! ---
//!
//! ## Argument Strategy
//!
//! The CLI defines **defaults and constraints**, so the rest of the system
//! can assume valid input.
//!
//! Examples:
//!
//! - `limit` defaults to a safe value
//! - `max_concurrency` is bounded to avoid overload
//! - `timeout` is parsed into a strongly-typed `Duration`
//!
//! This avoids the need for validation deeper in the pipeline.
//!
//! ---
//!
//! ## Extensibility
//!
//! New data sources can be added by:
//!
//! 1. Adding a new variant to [`Command`]
//! 2. Mapping it in `From<Command>`
//! 3. Implementing the corresponding logic in the core crate
//!
//! This keeps the CLI scalable as the project grows.
use Duration;
use ;
use LeadForgeCommand;
/// Top-level CLI configuration.
///
/// This struct is the entry point for parsing command-line arguments.
/// It delegates to subcommands defined in [`Command`].
/// Supported CLI commands.
///
/// Each variant corresponds to a different data source or operation.
/// Parses a timeout value (in seconds) into a [`Duration`].
///
/// # Errors
///
/// Returns an error if the input cannot be parsed as an integer.
///
/// # Example
///
/// ```
/// let duration = super::parse_timeout("10").unwrap();
/// assert_eq!(duration.as_secs(), 10);
/// ```
/// Converts a CLI [`Command`] into a domain-level [`LeadForgeCommand`].
///
/// This separates:
///
/// - **user input representation** (CLI)
/// - **execution logic** (core library)
///
/// This conversion layer ensures that the core system remains
/// independent from CLI concerns.