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
{{ message }}
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: