Why do merged routers use . and not /?

[mmkal]

In the docs (e.g. merging routers) routers are merged with a . prefix:

const appRouter = createRouter()
  .merge('users.', users) // prefix user procedures with "users."
  .merge('posts.', posts) // prefix poosts procedures with "posts."

Is there a reason for not using / which is a more standard way of delimiting url path segments? I have a vague memory of seeing an issue somewhere that would actually enforce this too. I ask because we're looking into using API Gateway with paths mapping to separate lambdas, all implemented by TRPC. Locally and in the type-system, we can just consider it one API, but each procedure can have granular permissions (read APIs not allowed to do dynamodb:PutItem, etc.).

I haven't tried to do API Gateway path mapping with dots yet, but based on the docs it looks not possible. Will we be able to use slashes for this use case? By that I mean

const appRouter = createRouter()
  .merge('users/', users)
  .merge('posts/', posts)

[KATT]

You are able to name your tRPC-router [...trpc].tsx and use / instead.

I actually had this originally; the reason I changed this myself is that you see the full path in the inspector rather than just the end part.

Note: I have not tested /-paths since adding batching support.

[mmkal]

Makes sense, thank you! Ok, I will try out slashes and can let you know if we see any issues with batching.

[KATT]

Should work - here's the source that should solve it if you're curious:

trpc/packages/server/src/adapters/next.ts

Lines 30 to 32 in 019cc9c

	if (Array.isArray(req.query.trpc)) {
	return req.query.trpc.join('/');
	}