ooni / ooni/explorer

Review eslint configuration and fix issues reported

Open
#433 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

chore
Dominant language
JavaScript
Stars
92
Forks
45
PR merge metrics
No merged PRs in 30d

Description

At some point, we stopped giving attention to errors and warnings from eslint. It is useful to a functioning linter.
What needs to be done:

  • Ensure rules and plugins enabled are sensible and align with widely adopted practices
  • Fix all issues reported
  • Integrate yarn lint into development, QA and release workflows

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.