Rename triggersRerun to cascade, and add new documentation #520
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.
First it was
soft
, then it wastriggersRerun
, now it'scascade
(note we haven't released yet, so none of these changes were breaking).This name came to me last night, and I kind of like it. I think
soft
is too vague and non-technical, buttriggersRerun
is just a mouthful (I've been typing it out a bunch, and it's been getting on my nerves).cascade
feels like it sort of gives an impression of what the thing does, and I think will be memorable and understandable once you've read the docs.Speaking of, I also rewrote the docs in a way that I hope is more clear.
Also adds some missing docs about
dependencies
andservice
to the configuration reference table.Addon to #237