Skip to content
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.

Add eslint to enforce coding conventions #31

Open
lauramosher opened this issue Sep 20, 2018 · 0 comments
Open

Add eslint to enforce coding conventions #31

lauramosher opened this issue Sep 20, 2018 · 0 comments

Comments

@lauramosher
Copy link
Contributor

Why

Coding conventions are documented best by a linter that can callout discrepancies early and often. In other Ministry Centered projects, eslint is the linter of choice. This sets the standard of the code. It removes any question of what is acceptable and what isn't. It also means that once we get to reviewing code to add to this project, we can spend more time reviewing the feature or patch rather than picking at coding conventions and style choices.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant