Dymanic Path Parameters

Describe the bug I have a route that has path parameters. I’ve run the generation tool to get specific use methods for this route. In my function setup I initially don’t have the value for these parameters. Ive set the use function to lazy:true so it doesn’t trigger right away. I have a function that is triggered by the user after they input the value for these parameters. I find that I cannot pass in these values when I call refetch because the absolute path has already been interpreted to be /some/path/undefined. This is likely because the code expects the path parameter when first construct it (due to the `/some/path/${pathParam}’ that is generated as the output from the generation step. My question is this:

How can I call refetch and replace the path parameter of generated functions dynamically. It’s not clear from the documentation. I’d love to use this library cuz it’s so close to what I need

[ApacheEx]

I have a scenario in where I need to make many submissions in a component, each for a different id, which is a path parameter. It’d be so nice to be able to do this imperatively in the mutate call.

if I understood your question properly it should be possible with current approach:

const { mutate } = useMutate({
  verb: 'POST',
  path: ({ id }) => `/api/v1/${id}/projects`,
});

// and then you just call.
mutate(body, { 
  pathParams: { id: 'whatever1' },
});

mutate(body, { 
  pathParams: { id: 'whatever2' },
});

mutate(body, { 
  pathParams: { id: 'whatever3' },
});

and also it should work for DELETE request since v14.4.0:

const { mutate } = useMutate({
  verb: 'DELETE',
  path: ({ id }) => `/api/v1/projects/${id}`,
});

// and then you just call.
mutate({}, { 
  pathParams: { id: 'whatever1' },
});

mutate({}, { 
  pathParams: { id: 'whatever2' },
});

mutate({}, { 
  pathParams: { id: 'whatever3' },
});

[zeorin]

Sorry to hear about your accident!

In my case this is not an ergonomic solution. The issue I have is how do I know when to change the path parameter.

It’s not just a case of not having one at the component mount and then getting it during the lifetime of the component. Using the lazy trick works well enough for that.

But when I have a list of things that I need to update, I need to loop through them. If I need to change the path parameter, currently, I don’t know when I can do this. Even if I manage to work around it somehow, that’s really not readable code, what I’m actually intending to achieve is not apparent.

A path parameter is conceptually not any different from a query parameter. If we allow for query parameters to be set when making the mutate call, why not a path parameter? Seems like a fairly arbitrary distinction.