T
tRPC
Issue Inferring Type on Frontend with ElectroDB Query Return Statement
Issue Inferring Type on Frontend with ElectroDB Query Return Statement
Hi all,
I am using ElectroDB to work with DynamoDB, and I have a Lambda function that uses tRPC that uses ElectroDB commands to read/write to my database.
I have a weird situation where the backend tRPC can infer the return type properly from my ElectroDB queries, but on the frontend (React), it says that the
useQuery() response is of type any
Attached screenshots show this
To fix it, I need to create a duplicate type of the return and then cast the return statement with it, like this is works. But I shouldn't need to do that.
Looking for more? Join the community!
T
tRPC
Issue Inferring Type on Frontend with ElectroDB Query Return Statement
T
tRPC
Issue Inferring Type on Frontend with ElectroDB Query Return Statement
Recommended Posts
Wrong JSON response when deployedWhen testing in localhost in dev mode there is no issue and the response is correct as expected.
BuExternal callsHi! I am using T3 stack, tRPC together with clerk, and i need to create users within the app, being Need help identifying the generic client side type of proceduresHi!
I think my question is better explained by what I'm trying to achive than anything else:
I likIs there a way to use versioning for procedures?I want to make multiple versions (v1 / v2) for a procedure, can i do it in procedure level?createSSGHelpersI'm trying to fetch data in getStaticProps and getting the issue "Promise<{ paths: { params: { id: nTRPC undefined when exportingHi i am working on merging routers from different files but when exporting the router property it co