feat!: expand default no-trailing-chars to include . ! ? and space#71
Merged
Conversation
Previously only '.' was forbidden by default. Most style guides prohibit all trailing punctuation and accidental trailing spaces are almost always mistakes, so the default now covers the common cases out of the box. Users who relied on '!' or '?' being allowed must explicitly configure: no-trailing-chars = ["."] or pass --no-trailing-chars "." to restore the old behaviour. Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
Coverage Report (Δ +0.0%)
|
||||||||||||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously only '.' was forbidden by default. Most style guides prohibit
all trailing punctuation and accidental trailing spaces are almost always
mistakes, so the default now covers the common cases out of the box.
Users who relied on '!' or '?' being allowed must explicitly configure:
no-trailing-chars = ["."]
or pass --no-trailing-chars "." to restore the old behaviour.