How can we fail hard when hostType and hostPath are mismatched?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 147
- Forks
- 45
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 4
Description
See discussion here: https://github.com/tc39/test262/issues/1147#issuecomment-315922125
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 the linked test262 discussion to determine the expected behavior for mismatched hostType and hostPath, then locate the corresponding validation in eshost. Done means the mismatch fails hard as agreed in that discussion; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100