Overriding context

[ryands17]

Hi,

I am using a database interface in the context of a procedure and I want to mock the interface in the tests by using call on the given procedure. Is it possible to override the context when calling call? I can't seem to do that as of now.

[dosubot[bot]]

Yes, you can override the context when calling a procedure with call in orpc. The call function accepts a context object as part of its options, so you can pass a mocked database interface in your tests. For example:

const output = await link.call(['procedure'], { value: 123 }, { context: { db: mockDb } })

If you need to intercept or manipulate context more deeply, you can use middleware with .use(({ context, next }) => { ... }) to modify or capture the context before the procedure runs. This pattern is shown in this discussion.

For mocking procedures, the recommended approach is to use the implement function, as described in the advanced mocking docs and discussed in this issue.

There are no indications that context is locked or cannot be set—passing a custom context per invocation is supported by design.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[unnoq]

Maybe client context can help: https://orpc.unnoq.com/docs/client/server-side#client-context
Or you can pass context each time you invoke a procedure: https://orpc.unnoq.com/docs/client/server-side#using-the-call-utility