About using ES6 features
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
In 2017, @gaearon added guidance on using new ES6 features in CONTRIBUTING.md. At that time, ES6 was still new to many people. But what about now?
Contributor guide
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 with CONTRIBUTING.md and its “Don’t use ES6 features when equivalent ES5 features have no downsides” section, which this issue identifies as the relevant guidance. Review whether the 2017 guidance still applies and determine the documentation change needed; done means the recommendation is clearly updated or confirmed for current ES6 usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100