如何改善既有 JS 代码修复常见的 ESLint 报警二
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 26
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
## 如何改善既有 JS 代码：修复常见的 ESLint 报警（二）
前言 ESLint 是目前最主流、最强大的 JS 代码校验工具。当我们的代码触发了 ESLint 的报警规则时，ESLint 就会提示错误时。 本系列文章将详细讲解那些需要手工介入修复的 ESLint 规则，帮助你顺利地把既有代码迁移到 ESLint 的保护之中。 no-return-assign 禁止 return…
December 23, 2017 at 02:46PM
via Instapaper https://github.com/cssmagic/blog/issues/78
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 linked article and the repository's existing reading-list entries. The issue does not identify a target file, requested edit, or acceptance criteria, so a maintainer must clarify what should be added or changed before work can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100