trpc - Invoking a route from within its own code

Question

trpc - Invoking a route from within its own code

After reviewing the information on this page, it appears that you can invoke another route on the server side by utilizing the

const caller = route.createCaller({})

method. However, if the route is nested within itself, is it feasible to achieve this by using the this keyword? If not, what is the alternative approach to calling a route sibling?

import { z } from "zod";

import { router, publicProcedure } from "../trpc";

export const exampleRouter = router({
  hi: publicProcedure.query(async () => {
    return "Hi there!";
  }),
  world: publicProcedure.query(async () => {
    return "World";
  }),
  hello: publicProcedure.query(async function () {
    const caller = this.createCaller({});
    const result = await caller.example.hi();
  }),
});

typescript trpc.io

Answer 1

Answer №1

Although I may not have the exact answer to your question, based on the provided link for Server Side Calls, it is advised that createCaller should not be utilized to call a procedure from within another procedure.

According to the documentation, using createCaller in this way can lead to unnecessary overhead as it may need to recreate context for each procedure call, even if only one API call is made from the client.

Instead of implementing code like your example:

import { procedure, router } from '../trpc'

export const myRouter = router({
    hi: procudure.query(() => 'hi'),
    hello: procedure.query(() => {
        const caller = createCaller({})
        return caller.myRouter.hi()
    })
})

It is recommended to use a different approach, such as:

import { procedure, router } from '../trpc'

const getHi = () => {
    return 'hi'
}

export const myRouter = router({
    hi: procudure.query(() => getHi()),
    hello: procedure.query(() => getHi())
})

In this revised example, the logic for retrieving the desired information (in this case, just 'hi' but it could be a database query) is abstracted so that the same code is called in each instance without the need for an additional procedure call.

Answer 2

Although I may not have the exact answer to your question, based on the provided link for Server Side Calls, it is advised that createCaller should not be utilized to call a procedure from within another procedure.

According to the documentation, using createCaller in this way can lead to unnecessary overhead as it may need to recreate context for each procedure call, even if only one API call is made from the client.

Instead of implementing code like your example:

import { procedure, router } from '../trpc'

export const myRouter = router({
    hi: procudure.query(() => 'hi'),
    hello: procedure.query(() => {
        const caller = createCaller({})
        return caller.myRouter.hi()
    })
})

It is recommended to use a different approach, such as:

import { procedure, router } from '../trpc'

const getHi = () => {
    return 'hi'
}

export const myRouter = router({
    hi: procudure.query(() => getHi()),
    hello: procedure.query(() => getHi())
})

In this revised example, the logic for retrieving the desired information (in this case, just 'hi' but it could be a database query) is abstracted so that the same code is called in each instance without the need for an additional procedure call.

trpc - Invoking a route from within its own code

Answer №1

Similar questions

A step-by-step guide on generating a TypeScript class using JSON data

Incorporating HTTP status codes into error handling

Exploring the functionality of angular reactive forms in creating intricate JSON structures

Using the ternary operator in React to implement inline styles

Utilize the global theme feature within React Material-UI to create a cohesive

An instance of an object is being added instead of parameters

Navigating with multiple parameters in Angular 7 routing

Retrieving the returned value from an Observable of any type in Angular Typescript (Firebase)

Mastering the art of correctly utilizing splice and slice

What is the best way to bundle a TypeScript package along with its dependencies for seamless integration with various Next.js projects on a local environment

Encountered an error while attempting to compare 'true' within the ngDoCheck() function in Angular2

Angular click switch Component keeps track of its previous state

Unable to make custom font work in TailwindCSS and ReactJS project

What is the best way to output data to the console from an observable subscription?

Unable to locate the module name loaded using require() function

Exploring .ENV Variables using Angular 2 Typescript and NodeJS

The canActivate function must be responsive to the true or false value of this.authService.isLoggedIn before proceeding

How can different styles be seamlessly combined when customizing Fabric components?

Is there a way to remove trigger characters in vscode api completion function?

Why is webpack attempting to package up my testing files?