Skip to content

Commit 731286a

Browse files
committed
make hooks messages configurable
...and update them to reflect current usage why: - these messages appeared to be just wrong (referencing `aide` instead of firstaide or an `update` command that doesn't appear to exist) - and in any case it's nice to have them all customizeable not just the getting_started message. based on the presence of the `Messages` struct I presume this was always intended how: - add fields to `Messages` struct, named based on the hook they are associated with - set sensible defaults for messages - add messages to the hooks scripts - splat configured messages into hooks scripts based on how it was done for the getting_started message docs: updated the readme to document messages configuration validation: tested new message configurations in a different project, `cargo test`
1 parent cca838c commit 731286a

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

src/config.rs

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,11 @@ impl AsRef<Path> for ParentDir {
5151

5252
#[derive(Debug, Deserialize)]
5353
pub struct Messages {
54+
#[serde(default)]
5455
pub getting_started: String,
56+
#[serde(default)]
5557
pub stale: String,
58+
#[serde(default)]
5659
pub inactive: String,
5760
}
5861

0 commit comments

Comments
 (0)