Calling procedures from others

D

Dani;•10/6/22, 1:17 PM

Check out

createCaller

createCaller

: https://trpc.io/docs/v10/server-side-calls#create-caller

Server Side Calls | tRPC

You may need to call your procedure(s) directly from the server, createCaller() function returns you an instance of RouterCaller able to execute query(ies) and mutation(s).

D

Dani;•10/6/22, 1:34 PM

Define it then

D

Dani;•10/6/22, 1:35 PM

const t = initTRPC.create();

const proc1 = t.procedure.query(({ input }) => {
  return {
    text: 'proc1',
  };
});

const proc2 = t.procedure.query(async ({ input }) => {
  const dataFromProc1 = await appRouter.createCaller().proc1();
  return {
    text: dataFromProc1.text,
  };
});

const appRouter = t.router({
  proc1,
  proc2,
});

const t = initTRPC.create();

const proc1 = t.procedure.query(({ input }) => {
  return {
    text: 'proc1',
  };
});

const proc2 = t.procedure.query(async ({ input }) => {
  const dataFromProc1 = await appRouter.createCaller().proc1();
  return {
    text: dataFromProc1.text,
  };
});

const appRouter = t.router({
  proc1,
  proc2,
});

const t = initTRPC.create();

const proc1 = t.procedure.query(({ input }) => {
  return {
    text: 'proc1',
  };
});

const proc2 = t.procedure.query(async ({ input }) => {
  const dataFromProc1 = await appRouter.createCaller().proc1();
  return {
    text: dataFromProc1.text,
  };
});

const appRouter = t.router({
  proc1,
  proc2,
});

const t = initTRPC.create();

const proc1 = t.procedure.query(({ input }) => {
  return {
    text: 'proc1',
  };
});

const proc2 = t.procedure.query(async ({ input }) => {
  const dataFromProc1 = await appRouter.createCaller().proc1();
  return {
    text: dataFromProc1.text,
  };
});

const appRouter = t.router({
  proc1,
  proc2,
});

D

Dani;•10/6/22, 1:39 PM

Actually this might not work

D

Dani;•10/6/22, 1:40 PM

Could be a bad idea, you might be able to extract the appRouter in a different file, but you might be hitting circular dependency errors

S

sachin•10/6/22, 1:42 PM

I think you're looking for

procedure.unstable_concat

procedure.unstable_concat

procedure.unstable_concat

procedure.unstable_concat

D

Dani;•10/6/22, 1:43 PM

Is it a bad idea to have multiple

t.router()

t.router()

t.router()

t.router() calls in a trpc application?

DDani;Is it a bad idea to have multiple `t.router()` calls in a trpc application?

S

sachin•10/6/22, 1:44 PM

nope, that's perfectly fine

S

sachin•10/6/22, 1:44 PM

That's the new ways of doing child routers (like

router.merge

router.merge

router.merge

router.merge in v9)

S

sachin•10/6/22, 1:45 PM

https://trpc.io/docs/v10/merging-routers#merging-with-child-routers

Mmowk Click to see attachment

S

sachin•10/6/22, 1:46 PM

Ah looking at this example, it's not what you want

S

sachin•10/6/22, 1:47 PM

using createCaller will work fine

S

sachin•10/6/22, 1:47 PM

(like Dani showed)

S

sachin•10/6/22, 1:50 PM

you don't need to include it in the initial router, you just need to include it in a router

S

sachin•10/6/22, 1:51 PM

that being said, I like exposing a function to call procedures on the procedure itself

S

sachin•10/6/22, 1:51 PM

will do a PR for that

S

sachin•10/6/22, 1:52 PM

No, it would go through all the middleware

S

sachin•10/6/22, 1:52 PM

middleware are attached to the procedure object itself

S

sachin•10/6/22, 1:52 PM

Ah yes

S

sachin•10/6/22, 1:53 PM

you'd have to pass in the context yourself though

S

sachin•10/6/22, 1:53 PM

sounds good