Spec Deviations
Open
Nobody has claimed this yet.
fetch
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
I think it would be good if we could agree on long term and short term spec deviations. Maybe base it on: https://deno.land/manual/runtime/web_platform_apis#spec-deviations?
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 by reviewing the issue proposal and the linked Deno spec-deviations guidance. The work would need an agreed classification of short-term and long-term deviations before implementation can begin; done would mean that the project’s deviations and their intended timeframes are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100