Component: HTTP Handlers
Open
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.2k
- Forks
- 115
- Avg merge
- 17h 28m
- Merged PRs (30d)
- 50
Description
This Issue exists to collect many items that relate to "Http Handlers" in Darklang
In Darklang-classic, HTTP Handlers only existed in our Cloud runtime (since that was the only runtime), but going forward we should have them supported for the Local/CLI runtime as well.
- bring them back locally, in some minimal capacity
- how do custom domains work in this new world? (see #3327)
- reimplement LibMiddleware (see #4151 and #3892. also #3407)
- revisit how we handle responses, esp errors (#4572)
- warm up BwdServer when it starts (see #3782)
- look at
opts.Limits.MaxConcurrentconnections(likely applies tobwdserver) - support HTTP Streaming
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
Review the linked issues (#3327, #4151, #3892, #3407, #4572, and #3782) and the existing HTTP-handler and BwdServer entry points first. Scope the Local/CLI support items and define completion separately for middleware, response errors, startup warm-up, concurrency limits, custom domains, and streaming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- api, backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100