Bret Little
Bret Little
It's just really hard to know what to compile to, because each runtime does env variables slightly different. Which is why we are pushing for some sort of unification standard:...
The challenge here is that non-200 responses often have JSON. `useShopQuery` returns an object. If it's a non-200 response, what should the hook return? 1. A string - now the...
@frehner in your research did you come across non-200 JSON responses? Let's consider all the scenarios `useShopQuery()` might trigger, and how it should behave: **1. Normal response** ```js // Response...
Thank you @frehner for more context. What do you think, should `useShopQuery` be throwing? Already it does for failed to fetch. But should it be throwing for non-200 responses?
My opinion: it's already hard enough to consistently and properly handle errors. If we force devs to handle errors in different ways, it's a lot less likely they will properly...
Would this be more of an enhancement than bug?
If we send to the client the separate layout maps, then the client should know during transitions which RSC request to make and which not to, so we wouldn't need...
> Define page level sub routes in page routes, for example, routes/index.server.tsx. These are sub routes that will only exist for this page route. Wouldn't we want some sub-routes to...
@mrkldshv I don't think so, just the time and bandwidth to do it.
@beardage that would be great! Maybe start with an outline or rough draft and I can help fill in the holes.