-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adopt StandardJS #448
Comments
Just because the project doesn't use StandardJS doesn't mean it doesn't have a standard style (and linting). This project's style guide was adapted from Airbnb's (see |
Hi, thanks for the suggestion. We’ve taken a slightly different stance on linting in this project. We want to stay out of the semicolon debates. It’s fine if you care about enforcing style, and you can use StandardJS yourself in the created projects, but beginners will just be frustrated that the example they copy and pasted from StackOverflow emits 50 warnings. This will lead them to ignore warnings completely, which is not what we want to do. We started with |
While I like StandardJS, I really appreciate the rationale given, it's very thoughtful. Thanks. |
I've found StandardJS to be a godsend, because its strong opinions mean I don't have to have opinions about styling.
Given the ambition of this project to influence beginners, I would submit that StandardJS would be a great influence on new devs.
See http://standardjs.com/ for details.
Specifically, for this project, I think this would mean at least:
standard
as part of the on-change handling.I expect discussion ;-)
The text was updated successfully, but these errors were encountered: