Accessing CallContext from handlers

Open
#7 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
backend-api-design

Research direction

Start by reading the referenced unenv src/runtime/fetch/call.ts createCall implementation and the linked Nitro Cloudflare entry to understand how CallContext is currently used. Compare the proposed request-property approaches and check existing handler behavior; done means the context properties are accessible from the actual handler without breaking current requests.

Written by the indexing model from the issue text.

Description

CallContext, which is the argument of the handler created by createCall, can have additional properties, but those properties are not passed to the actual handler (such as h3 app) and are not accessible.

Cloudflare Workers, for example, may need access to event and I want a way to access this.
https://github.com/unjs/nitro/blob/v0.4.4/src/runtime/entries/cloudflare.ts#L26

One suggested solution is to add context prop to req.
(req as any)._callContext = context, or (req as any)[symCallContext] = context (using symbol)

Dominant language
TypeScript
Stars
17
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from unjs/node-mock-http

All issues in unjs/node-mock-http

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.