popcodeorg / popcodeorg/popcode

More jshint errors

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue help wanted
Dominant language
JavaScript
Stars
191
Forks
143
Avg merge
4d 11h
Merged PRs (30d)
5

Description

https://trello.com/c/JuoHRCmt/93-more-jshint-errors

Go through the jshint code and audit all error message it is able to generate. Integrate all that are useful to us.

The mappings for jshint errors live here; the validation tests live here (though check the other language validation tests, which are more robust, for inspiration). The translation file that generates the error messages is here.

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.

Research direction

Start by auditing the JSHint mappings in src/validations/javascript/jshint.js against the errors JSHint can generate. Read the validation tests in src/validations/javascript.js and compare them with the other language validation tests, then update the relevant entries in locales/en.json. Done means useful JSHint errors are integrated and covered by validation tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
localization, testing, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.