Changelog - 2026-09-08
A namespace holding a dot is refused
Behavior ChangeIn one line. BindingNamespaces.createNamespace throws when the name holds a ., holds whitespace, or is empty, so a binding no longer goes missing silently.
ts
BindingNamespaces.createNamespace({ name: 'services' }); // 'services'
BindingNamespaces.createNamespace({ name: 'acme.services' }); // throwsWhat changed
- A bad namespace throws. A binding tags itself with the first dot-separated segment of its key, so
acme.serviceswas taggedacme. Nothing drained that tag, and the dependency came back undefined at request time. The mistake now throws at class-initialization time. BindingNamespaces.CONFIGURATION. New. Resolves to'configurations'.z.ZodTypein public types.TInferSchema,TCustomizableRouteConfig(response.schema),defineSearchRouteConfigs()(selectSchema) andderiveSearchDocumentSchema()namez.ZodTypewhere they named the deprecatedz.ZodTypeAny. The two are one type in zod 4, so your code compiles either way.
Who is affected
- You call
createNamespacewith a literal name. Check the name is a single segment. Every namespace IGNIS ships already is. - You pass a namespace string to
BindingKeys.build. Nothing changed.buildstill accepts''to produce an un-namespaced key. - Everyone else. Nothing to do. No symbol was renamed or removed.
See also
- Dependency Injection - binding keys, namespaces, and how a tag is derived