realm vs async context
Open
Nobody has claimed this yet.
fetch
question
spec
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
The fetch spec mentions "realm" and "relevant realm" a lot. I assume this is something similar to async context in NodeJS? Should we try to translate the API and implement accordingly?
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
The issue names no files or tests. Start by reading the Fetch specification sections that define “realm” and “relevant realm”, then compare those concepts with NodeJS async context. Done means the relationship is decided and any resulting API or implementation work is explicitly scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100