This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
Map insert_final_newline
to insertFinalNewline
#8
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 PR proposes to read editorconfig's
insert_final_newline
when it is set tofalse
.Motivation
I know this PR might sound odd. Because Prettier follows unix guideline regarding the final newline (Prettier doc reference).
Yet, handlebars / glimmer does not follow this standard (see reference here) because it would insert empty nodes at the bottom of the component's file.
So for now Prettier respects this handlebars choice and remove the final newline. But this is somehow inconsistent with other languages and it creates discussion / lack of understanding etc. One possibility could be to respect instead the user choice made with
.editorconfig
'sinsert_final_newline
option. Hence this PR.In a follow-up, we'd use that
insertFinalNewline
option in handlebars printer to insert or remove the final newline.Links