swift-server / swift-server/swift-http-server
Implementation-specific request contexts
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 44
- Forks
- 13
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 8
Description
Opening this issue to discuss what the best shape for providing implementation-specific information on the RequestContext should be: task locals, an existential on the current RequestContext, something else...
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 at the RequestContext entry point and compare the task-locals and existential approaches named in the issue. The work is complete when the project has an agreed shape for exposing implementation-specific information on RequestContext.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100