I managed to get this working by doing this as shown by the screenshot. Is this the way to go, can I build some auxiliary types to use this structure to infer inputs/outputs?
It is often useful to wrap functionality of your @trpc/client or @trpc/react api within other functions. For this purpose, it's necessary to be able to infer input types, output types, and api paths generated by your @trpc/server router.