Consider extending BindArgsSchemas

[bryantabaird]

I found myself trying to extend bindArgs schemas, similar to schema extension, so I have a suggestion for the team to consider implementing similar extension functionality as well for bindArgsSchemas

My use case is as follows. I have a resource management URL as follows: /parent/{parentId}/child/{childId}.

I'm creating a high level client for the parent, something like:

const parentIdSchema = z.string();

export const parentClient = baseClient
  .bindArgsSchemas<[parentId: z.ZodString]>([parentIdSchema])
  .use(() => { /* Validate authenticated user has access to this parent via the parent id*/ })

Assuming editParent included an action to the parentClient, the parent client code would then call:

// parentId inferred from URL
const boundEditParent = editParent.bind(null, parentId);

I was planning for the child client to extend from the parent, like so:

const childIdSchema = z.string();

export const childClient = parentClient
  .bindArgsSchemas<[childId: z.ZodString]>([childIdSchema])
  .use(() => { /* Validate authenticated user has access to this child via both the parent and child ids */ })

Assuming editChild included an action to the childClient, the child client code would then call:

// parentId and childId inferred from URL
const boundEditChild = editChild.bind(null, parentId, childId);

But the child bindArgsSchema is overriding the bindArgsSchema from the parent. Is this correct? If so, would it be recommended for me to modify the editChild function to override and include both? Something like:

const parentIdSchema = z.string();
const childIdSchema = z.string();

export const childClient = parentClient
  // Override the previously declared bindArgs schema in the parent client
  // There is a bit of duplication, but this might be feasible?
  .bindArgsSchemas<[parentId: z.ZodString, childId: z.ZodString]>([parentIdSchema, childIdSchema])
  .use(() => { /* Validate authenticated user has access to this child id */ })

Or maybe there is another approach that I did not consider. Perhaps I could try to update my child ids to not depend on the parent ids. But this might not always be a viable workaround.

All the same, thank you 🥇