TRPC Fetching pattern
Question about helpful trpc patterns.
Does .useQuery on the client side render multiple times (initial data state, isLoading state, error or promise fulfilled state)?
Right now I'm fetching SSR an initial data state, and then passing that into the client component, as the initial data- and then doing a useQuery for my useUtils invalidate will work correctly and data wont be stale.
Can I simply just make the initial state an empty key value object of the output, or would this become problematic later on down the line- or is having two calls, one at nav and one on mount overkill?
Does .useQuery on the client side render multiple times (initial data state, isLoading state, error or promise fulfilled state)?
Right now I'm fetching SSR an initial data state, and then passing that into the client component, as the initial data- and then doing a useQuery for my useUtils invalidate will work correctly and data wont be stale.
Can I simply just make the initial state an empty key value object of the output, or would this become problematic later on down the line- or is having two calls, one at nav and one on mount overkill?
