Optimal approach to fire a second query that depends on the result of a first query?
I'm building out the messaging portion of my SaaS, and first I send a query for the chats, and then after that I retreive the details of those involved in the conversation via a second query. My standard implementation would be to use a useEffect hook with the chats as a dependency, but wondered if there was a better version of doing this in wasp?
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.