provide with header access

[LucWag]

Hey,
we use React in combination with Remix, which creates the problem that the implementation for ExpressZodAPIClient is too static if we want to dynamicly change the headers.
Is it possible to extend the Implementation interface like:
export type Implementation = ( method: Method, path: string, params: Record<string, any>, headers?: Record<string, string> ) => Promise<any>;

To clarify the problem with Remix:

• The client (browser) communicates with Remix via loaders and actions. Also sends auth cookies for APIs.
• Remix is responsible for fetching/sending data from/to differnent APIs by using the ExpressZodAPIClient.
• Multiple clients communicate with one/multiple Remix servers. Therefore one static Implementation on Remix side is not capable to handle multiple clients.

[RobinTail]

Hello @LucWag ,

could you please clarify:

• Are the names of those headers all starting with X-?
• is there any entity besides express-zod-api that is reading those headers on backend?

[RobinTail]

What I'd like to propose to you, @LucWag, is:

1. Describe the required headers as the endpoint/middleware inputs (hoping they are all custom, start from X-)
2. Adjust inputSources in your config to handle headers as an input source
3. The generated client will be typed along with those headers as the part of Input
4. Then you make an implementation that receives the params that you may partially put into the headers when they start from X- or belong to some list of known headers.

Moreover, express-zod-api may take them also from request body, it does not matter for the framework because all the configured inputSources are combined. That trick, however, won't work if something else is expecting the data to be specifically in the headers.

Let me know what you think.

The idea of passing other things to .provide() may only be implemented in the next major, which is coming soon in February.
I will think about it as well.

[LucWag]

Hi @RobinTail ,
thanks for your quick response.
For now this might be a solution which can be implemented and used by us, but in the near feature we will also have clients (without Remix) which communicate directly with the APIs.
On API side it would still be possible to check for cookies/headers in addition to extending the input zod schema. Each API would have to double check if any authorization information was either passed by cookie, header or body.
As you can see it requires double implementation and doesn't feel like clean code.
An extention of .provide() in the next major would be awesome.

In addition: For now we use custom headers/tokens like "company abc"