You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
99% of package.json files, use a 2 space indent, and so the default for most editors is that.
tns create --ng however, generates a package.json file with 4 space indent, but without an indication on how editors should treat it, it's a very reasonable default for them to use the norm. Which means that as you begin to work with the files, the editor is trying to make unecessary formatting changes to the code.
Describe the solution you'd like
As part of creating a new project, tns create also generates a .editorconfig file that has settings matching the files that get generated. E.g.
[*.json]
indent_style = space
indent_size = 4
This has two clear advantages:
Whatever editor a deveolper uses, it will work seamlessly out of the box with a project created tns create
Teams have a clear place to change the preferences if they decide that it should behave differently, and it will not effect the style settings on any other project.
Describe alternatives you've considered
Generate package.json files with indent: 2 since it is the norm on npm.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
99% of package.json files, use a 2 space indent, and so the default for most editors is that.
tns create --ng
however, generates a package.json file with 4 space indent, but without an indication on how editors should treat it, it's a very reasonable default for them to use the norm. Which means that as you begin to work with the files, the editor is trying to make unecessary formatting changes to the code.Describe the solution you'd like
As part of creating a new project,
tns create
also generates a.editorconfig
file that has settings matching the files that get generated. E.g.This has two clear advantages:
tns create
Describe alternatives you've considered
Generate
package.json
files withindent: 2
since it is the norm on npm.The text was updated successfully, but these errors were encountered: