Repository navigation
feat: add eofNewLine config - #66
Merged
Merged
Conversation
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
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.
Closes #22
Adds an
eofNewLineoption to control the newline at the end of the file:"always"(default) - always end the file with a newline. This is the existing behaviour."maintain"- end the file with a newline only when it already ends with one."never"- never end the file with a newline.This is useful for files like
package.json, where package managers often remove the trailing newline when adding or removing packages.maintainchecks the text after the BOM is stripped and the package.json conventions are applied (the conventions keep what trails the root value). It counts a\nor a lone\ranywhere in the trailing whitespace.newLineKind.