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

Add eslint to enforce coding conventions #31

Description

@lauramosher

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions