feat(rules): add regex support for [subject|header]-full-stop rules #818
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.
Description
This allows usage of string regular expressions as
value
forsubject-full-stop
andheader-full-stop
rules.Motivation and Context
We, internally, allow a range of stops. The current rule, however, allows providing one stop character which is restrictive, at least, in our use-case.
Yet, I'm not sure if it's a better fit for a plugin or the core.
Usage examples
How Has This Been Tested?
By adding new test cases.
Types of changes
Checklist