\r\n}\r\n\r\n```",[3088],{"name":3033,"color":3034},"examples-v10-next-prisma-starter-sqlite","[RFC] `invalidateQueries` and other `react-query` `useContext()`-fns","2022-08-25T23:31:17Z","https://github.com/trpc/examples-v10-next-prisma-starter-sqlite/issues/3",0.7544877,{"description":3095,"labels":3096,"number":104,"owner":3022,"repository":3097,"state":3045,"title":3098,"updated_at":3099,"url":3100,"score":3093},"Just dumping some thoughts / half-baked ideas here\r\n\r\n\r\n\r\n\r\n- ~~With RSC - is there a point of tRPC? Is there a \"lighter\" approach that might be nice(r)?~~ Maybe, but not for all\r\n- ~~With RSC - is there a point of react-query?~~ yes, there's still client components\r\n- Will there be a way to sync state and make sync the underlying state of the queries from RSC -> client & make *isomorphic* components?\r\n - Biggest question - unsure how state sync can work from a root `\"use client\"` Provider that renders on the server to the client that uses it.\r\n- Will importing the full router on every RSC-request add any significant overhead?\r\n- ~~Will React Context providers be available on the server? If so, it be possible to do any \"isomorphic\" context providers? Will components be able to be isomorphic?~~ This was a misconception. We'll do a root `\"use client\"` component & likely not sync state from actual RSC-components to client\r\n - If query state could be synced from server to client and context providers + components could be isomorphic, we could do stuff like using optimistic updates of a component that was initially rendered on the server.\r\n- How to deal with caching? \r\n- [..]",[],"next-13","Open questions","2022-11-28T10:46:18Z","https://github.com/trpc/next-13/issues/3",{"description":3102,"labels":3103,"number":3104,"owner":3022,"repository":3023,"state":3045,"title":3105,"updated_at":3106,"url":3107,"score":3108},"Copied this exact usage when passing path params but I'm getting a 404 error. \r\n```tsx\r\nsayHello: t.procedure\r\n .meta({ openapi: { method: 'GET', path: '/say-hello/{name}' /* 👈 */ } })\r\n .input(z.object({ name: z.string() /* 👈 */, greeting: z.string() }))\r\n .output(z.object({ greeting: z.string() }))\r\n .query(({ input }) => {\r\n return { greeting: `${input.greeting} ${input.name}!` };\r\n });\r\n```\r\n\r\n\r\n\r\n(I don't get a 404 error when I don't use path params).\r\n(I'm using this on NextJS)",[],288,"Error 404 when I use path params","2023-04-24T08:16:58Z","https://github.com/trpc/trpc-openapi/issues/288",0.7545653,["Reactive",3110],{},["Set"],["ShallowReactive",3113],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8ob-vClV6jDIP2kPJxbI_x6VmXdtHxf0KTJDHF5WctM":-1},"/trpc/trpc-openapi/425"]