trpc/react-query render logic
I've made the attached diagram to try and explain the scenario, but for additional context, my issue is this:
I have a page that conditionally renders two main views. the editable view submits a form, after which I would like to render the opposite view, but with the new data.
currently, i'm invalidating on success, though it seems that the completion of invalidate doesn't ensure that my other component will have refetched its data yet. my idea would then be to block my readonly component on both loading AND fetching. the issue here is that toggling between views when there is not a form submission ends up showing a load state, presumably because isRefetching is true even if its fetching from cache. ...
Data operations in tRPC router
Hi guys, I'm wondering if a router is a good place to operate on data.
That's a dummy example, it works. But in more complicated calculations is it a good practice?...
Typing Props
I have a query that is returning an array of items. I'm then mapping over that array and rendering elements in a child component. I did some wacky stuff to get the type from the api but that felt VERY wrong. Currently just passing an id and refetching inside the child, but that also seems wrong. What is the best practice here?
middleware does not run on index page
Here's the middleware config
```ts
export const config = {
matcher: [
/*...
should I use ctx or api?
whats the difference between me using api.events.getEvent.cancel() vs ctx.events.getEvent.cancel()?
why does one work and not the other?
isn't api in ctx, so shouldn't I be able to just use api and not ctx?
which one should I be using?...
