From b7d4dc7642ff25dbdca132e89705f40cfa0f0c9d Mon Sep 17 00:00:00 2001 From: Robert Soriano Date: Mon, 9 Jan 2023 10:33:07 -0800 Subject: [PATCH] Update 1.composables.md --- docs/content/1.get-started/5.tips/1.composables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/1.get-started/5.tips/1.composables.md b/docs/content/1.get-started/5.tips/1.composables.md index 02929a0..bf89123 100644 --- a/docs/content/1.get-started/5.tips/1.composables.md +++ b/docs/content/1.get-started/5.tips/1.composables.md @@ -7,7 +7,7 @@ title: Composables It is often useful to wrap functionality of your `@trpc/client` api within other functions. For this purpose, it's necessary to be able to infer input types and output types generated by your `@trpc/server` router. ::alert{type="info"} -[createTRPCNuxtClient](/get-started/client/create) adds a `useQuery` method built on top of [useAsyncData](https://nuxt.com/docs/api/composables/use-async-data/). +[createTRPCNuxtClient](/get-started/client/create) adds a `useQuery` method built on top of [useAsyncData](https://nuxt.com/docs/api/composables/use-async-data/). You might not need this. :: ## Inference Helpers