At what point is it acceptable to use new syntax or interfaces?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
(prompted by https://github.com/tc39/test262/pull/3192#discussion_r707369883)
To what extent are non-original or "new" features appropriate in testing unrelated older functionality? For example, should an intentionally limited implementation like Hermes or QuickJS or XS or a new in-progress implementation be unable to even run tests covering ES6 functionality because it does not yet support class private fields or String.prototype.matchAll?
Ideally, this is resolved by updating CONTRIBUTING.md with appropriate guidance.
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
Read the discussion linked from the issue, especially the comments on test262 pull request 3192, then inspect CONTRIBUTING.md. Use the unresolved guidance question to determine the appropriate policy for newer syntax in tests of older features. Done means CONTRIBUTING.md documents the agreed guidance clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100