/pages/[tenantKey]//pages/[tenantKey]/ path. The tenantKeytenantKey describes which tenant we are working with at the moment. I'm messing around with Next.js + tRPC, and I would love to be able to access the Next.js Router (to access the tenantKeytenantKey) in a generic way when accessing the tRPC client. Using the tenantKeytenantKey in the path, I could automatically send a header, X-Tenant-KeyX-Tenant-Key, that the server side of tRPC could look at when generating the appropriate context.useQuery(...)useQuery(...) features. Using it would be like this:@trpc/next@trpc/next library from scratch? Join the Discord to ask follow-up questions and connect with the community