pytest-dev / pytest-dev/pytest-html
Expand ESLint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 779
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
ESLint was introduced in https://github.com/pytest-dev/pytest-html/pull/367
This first pass included almost all relevant ESLint sections except for the following:
The following three rules were also skipped, since they involved making broad changes across the JS code. It would be better to submit them as separate PRs:
- https://eslint.org/docs/rules/no-use-before-define
- https://eslint.org/docs/rules/#strict-mode
https://eslint.org/docs/rules/camelcase - PR open in https://github.com/pytest-dev/pytest-html/pull/410- Done
I'll be adding all of the above, one PR per bullet point when I find the time to.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ESLint setup introduced in pull request 367 and the Stylistic Issues and ECMAScript 6 rule sections linked in the issue. Treat the remaining rule groups as separate changes, and consider the work done when the selected rules are configured and the JavaScript linting passes without requiring unrelated broad edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100