Closed liyofx closed 7 months ago
@liyofx Hi,
This is expected. The Strict
function discards all compositing symbols TypeBox uses to operate. Note that these symbols are used to compose schematics, differentiate between ambiguous static types, but are also used to type check. As such, calling Strict on a type will result in the type no longer being considered valid.
The Strict
function was historically used to resolve issues in Ajv where unknown properties (i.e. these symbols) were flagged in Ajv strict
mode as invalid. More recent versions of TypeBox use a different strategy that mitigates the need to Strict before use, so the function is largely kept around for backwards compatibility (notably for large early adopter projects which still use it for couple of things)
All this said, the Strict function shouldn't be used if working against TypeBox's compiler and value modules.
Hope this brings some insight! Cheers! S
@liyofx Heya,
All things are working as expected here. Will close off this issue for now, but happy to field any additional questions you might have on this thread.
Cheers! S