jfmengels/eslint-ava-rule-tester

Ability to set defaults

Open

#1 opened on Aug 4, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (14 stars) (4 forks)user submission
enhancementhelp wanted

Description

https://github.com/sindresorhus/eslint-plugin-xo/pull/45#discussion_r73125085

I don't see a problem with this as long as it's clearly documented. The original RuleTester isn't very well documented anyways. We should improve upon it where it makes sense.

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
knowledge of ESLint RuleTesterfamiliarity with AVA test framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
First, read the referenced PR discussion at sindresorhus/eslint plugin xo/pull/45#discussion r73125085 to understand what default settings are being proposed. Then, examine the current source code in the eslint ava rule tester repository, specifically the RuleTester implementation, to identify where defaults could be added. Look at any existing tests to understand the testing patterns. Finally, consider documenting the new defaults clearly as suggested in the issue.