make hooks messages configurable #162
Open
Commits on Oct 25, 2023
-
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`
-
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`
-
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 - use serde default attributes to allow mixing defaults and custom messages without errors - 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`
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.