Example of useForm with mutation using different resource, than what's used to fetch the data?

[vinclou]

Problem Space

Most API's often include Internal/Hidden routes inaccessible in the public API schema

A REST endpoint used to query the data often differs from the endpoint used to patch/delete/post data. (While get routes can be also hidden from public API)

Let's say I need to fetch a user at Get: Public/User/{id}, but to modify a user I need to use Patch: Internal/User/{id}

So you give a resource to useForm:

	const {
		formProps,
		mutationResult,
		show
	} = useForm<TData, TError, TUpdates>({
		action: 'edit',
		resource: `Public/User/${showId as string}`,
                // mutation needs to happen at Internal/User/${showId as string}
		queryOptions: {
			enabled: Boolean(showId)
		},
	})

But then useMutation uses the same route to PATCH the data as useQuery, which I see as an antipattern if u can't override a given mutation from formProps with ur own, or explicitly tell it to use a different API req. Or even an advice.

Any advice on how to deal with such situations?

[omeraplak]

Hey @vinclou ,
I don't know how common this use-case is but you can deal with this using data hooks. Override your form's onSubmit and call your desired data hook (useUpdate, useCreate, etc.). For data store invalidation, you can use useInvalidate. I hope it will be useful for you 💥

[vinclou]

True, that's how I solved the problem yesterday, I was just double checking if I'm missing anything