Replaced eslint with Standard for formatting #1
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
I replaced the eslint coding style with Standard as I genuinely believe it to be the superior style. Primarily due to the lack of project specific settings, you cannot change the coding style so it's always the same. This means I updated the package.json to include the correct dependency and added a script called format. Running npm format will use Standard to automatically fix many formatting errors. I also added Josh and myself to the package.json as contributors.
Member
Author
|
If we need semicolons due to how much everyone else is used to them, we also have semistandard, which is the same thing with semicolons sprinkled in. |
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.
I replaced the eslint coding style with Standard as I genuinely believe it to be the superior style. Primarily due to the lack of project specific settings, you cannot change the coding style so it's always the same.
This means I updated the package.json to include the correct dependency and added a script called format. Running
npm formatwill use Standard to automatically fix many formatting errors.For more information on the Standard coding style, you can check out the repository available here: https://github.com/standard/standard.
I also added Josh (coder4life) and myself to the package.json as contributors.