Skip to content

GitHub Actions: Implement ESlint #1442

@akibrhast

Description

@akibrhast

Dependency

#1441

Overview

We need to implement a linter for our javascript code to standardize and maintain the code properly.

Action Items

  • Create a list of possible bare minimum esLint settings that we can turn on
    • During one of the developer meetings, discuss the possible settings with the team and finalize a list of settings to implement
    • You may reference and use the list from this comment
  • Implement a GitHub action that triggers on pull request or on push to the gh-pages branch
    • The action should lint javascript files. The recommended tool for linting is Super Linter
    • Create the action as part of your local fork of the repository
    • Run the action on js files that should end in a success, and ensure that the action actually succeeds
    • Run the action on js files that should end in a failure, and ensure that the action fails properly based on the correct settings
    • Demo your prototype to the team and/or the technical lead to get approval
    • After approval, create a PR for review
    • Ensure that the linter does not trigger or break on liquid syntax
  • For merge team: Release dependency on Create a wiki page for linters used by the HfLA website team #3230

Resources/Instructions

Additional resources:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Ice box

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions