Consider using EditorConfigs `insert_final_newline` when generating new version.json with nbgv
See original GitHub issueIt would be cool, if nbgv set-version
would respect insert_final_newline = true
. 😉
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Why does the editor insert a final newline for JSON files ...
I have the following .editorconfig : ... insertFinalNewline": false,. When selecting all content of package.json and choosing Format ...
Read more >Using the nbgv .NET Core CLI tool
The prepare-release command supports this working model by taking care of creating the release branch and updating version.json on both branches. To prepare...
Read more >EditorConfig settings - Visual Studio (Windows)
Settings in EditorConfig files let you maintain consistent coding styles and settings in a codebase, such as indent style, tab width, ...
Read more >EditorConfig
EditorConfig is a file format and collection of text editor plugins for maintaining consistent coding styles between different editors and IDEs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@yannduran for me, it’s because of the scc diffs that show up later. I like trailing newlines so that adding another line doesn’t have to change the last line as well as add the new one. I just want to add the new one.
That’s also why I add trailing commas to lists where each item is on its own line.
That’s a good explanation why I want it too: https://stackoverflow.com/a/729795
In short: Because of the POSIX standard