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
//! Consumer-facing ports — the types consumers need to type-annotate when
//! using cornichon.
//!
//! Per the pragmatic trait-split decision, cornichon depends directly on
//! `ratatui` and `crossterm` rather than abstracting them behind consumer-
//! owned traits. The "ports" in this crate are therefore *type re-exports*
//! rather than trait interfaces: consumers don't need to add ratatui /
//! crossterm as direct dependencies to write
//!
//! ```rust,ignore
//! fn handle(event: cornichon::ports::KeyEvent) { ... }
//! ```
//!
//! but they only need to if they want to *construct* events themselves
//! (most users just forward events from `crossterm::event::read`).
//!
//! # Layout note
//!
//! If we ever move to a strict consumer-owned-traits design (one render
//! trait per menu, owned by the application layer), the `ports::render`
//! module is where those traits will live. The current shape is the
//! pragmatic minimum that still respects the
//! `src/{domain,ports,application,adapters}` layout standard.
pub use ;
pub use ;
pub use ;
pub use drive_until_action;