Problem
When multiple specs share a single schemas.ts, schema lookup matches a bare ${Type}Schema name (fastify-type-provider.ts:295) with no per-spec namespace, so spec1.GetUser and spec2.GetUser both resolve to GetUserSchema with no way to disambiguate.
Proposed fix
Add a spec_prefix config field that feeds the lookup (e.g. PublicApiGetUserSchema vs AdminApiGetUserSchema).
Notes
Niche: most multi-spec setups give each spec its own schemas.ts, which already works. Defer until someone hits it. Effort: medium. Source: post-#328 architecture review.
Problem
When multiple specs share a single
schemas.ts, schema lookup matches a bare${Type}Schemaname (fastify-type-provider.ts:295) with no per-spec namespace, sospec1.GetUserandspec2.GetUserboth resolve toGetUserSchemawith no way to disambiguate.Proposed fix
Add a
spec_prefixconfig field that feeds the lookup (e.g.PublicApiGetUserSchemavsAdminApiGetUserSchema).Notes
Niche: most multi-spec setups give each spec its own
schemas.ts, which already works. Defer until someone hits it. Effort: medium. Source: post-#328 architecture review.