tRPC•3y ago•

7 replies

How can I use `onSettled` in the `experimental_createTRPCNextAppDirClient`?

Context

I want to migrate the following trpc/client hook to the experimental version

const searchMandate = api.mandate.search.useMutation({
    onSettled: (data) => {
      searchQueryMethods.reset();
      data?.length
        ? toast.success(`Found ${data?.length} companies.`)
        : toast.message("No companies found.");
    },
  });

const searchMandate = api.mandate.search.useMutation({
    onSettled: (data) => {
      searchQueryMethods.reset();
      data?.length
        ? toast.success(`Found ${data?.length} companies.`)
        : toast.message("No companies found.");
    },
  });

However, the

experimental_createTRPCNextAppDirClient

experimental_createTRPCNextAppDirClient

exposes the

mutation

mutation

directly, not the
useMutation
useMutation
anymore

Problem
- the

ClientContext

ClientContext

from the

ProcedureArgs

ProcedureArgs

doesn't seem to accept any callback configuration? (the

...args

...args

type for the

mutation

mutation

on the consumer is

any

any

but I assume it's still the actual type)
- checking the trpc example I see it show cases a

mutation

mutation

without any callback configs (https://github.com/trpc/trpc/blob/cf5783bebbec295db84ec7b5dafa33da114379ad/examples/.experimental/next-app-dir/src/app/post-example/page.tsx)
- I also peeked at @julius's awesome acme-corp but it's similar to the trpc example in that it doesn't make use of callbacks.

version:

"@trpc/client": "11.0.0-alpha-next-2023-11-01-15-02-16.94"

"@trpc/client": "11.0.0-alpha-next-2023-11-01-15-02-16.94"

GitHub

trpc/examples/.experimental/next-app-dir/src/app/post-example/page....

Move Fast and Break Nothing. End-to-end typesafe APIs made easy. - trpc/trpc

trpc/examples/.experimental/next-app-dir/src/app/post-example/page....

How can I use `onSettled` in the `experimental_createTRPCNextAppDirClient`?

Context

I want to migrate the following trpc/client hook to the experimental version

const searchMandate = api.mandate.search.useMutation({
    onSettled: (data) => {
      searchQueryMethods.reset();
      data?.length
        ? toast.success(`Found ${data?.length} companies.`)
        : toast.message("No companies found.");
    },
  });

const searchMandate = api.mandate.search.useMutation({
    onSettled: (data) => {
      searchQueryMethods.reset();
      data?.length
        ? toast.success(`Found ${data?.length} companies.`)
        : toast.message("No companies found.");
    },
  });

However, the

experimental_createTRPCNextAppDirClient

experimental_createTRPCNextAppDirClient

exposes the

mutation

mutation

directly, not the
useMutation
useMutation
anymore

Problem
- the

ClientContext

ClientContext

from the

ProcedureArgs

ProcedureArgs

doesn't seem to accept any callback configuration? (the

...args

...args

type for the

mutation

mutation

on the consumer is

any

any

but I assume it's still the actual type)
- checking the trpc example I see it show cases a

mutation

mutation

"@trpc/client": "11.0.0-alpha-next-2023-11-01-15-02-16.94"

"@trpc/client": "11.0.0-alpha-next-2023-11-01-15-02-16.94"

GitHub

trpc/examples/.experimental/next-app-dir/src/app/post-example/page....

Move Fast and Break Nothing. End-to-end typesafe APIs made easy. - trpc/trpc

How can I use `onSettled` in the `experimental_createTRPCNextAppDirClient`?

Similar Threads

How can I use `onSettled` in the `experimental_createTRPCNextAppDirClient`?

Similar Threads

Similar Threads

Similar Threads