Type.RegExp fails at Ajv compilation about env-schema HOT 3 CLOSED

I would like to close this issue (no privilege for me) because we do not support the type that is not JSON Schema.

Type.RegExp return type: 'RegExp' instead of type: 'string'.
https://github.com/sinclairzx81/typebox/blob/master/src/type/regexp/regexp.ts#L55

cc @sinclairzx81 It there any reason to use RegExp instead of string?

from env-schema.

@climba03003 Hi,

This was updated in 0.32.0 with the RegExp type moved to the [JavaScript] type set to draw greater distinction between the regular expressions supported by Json Schema, and expressions supported by the full ECMA 262 syntax. The subset syntax supported by Json Schema (and Ajv) can be found here

The general recommendation is to use Type.String({ pattern: '...' }) to ensure compliance with the specification moving forward. However the RegExp type does enable full support of the full ECMA 262 syntax, including UTF-16 (Unicode) and flags at a cost of being "non-standard". As such, it only works with the TypeBox Value and TypeCompiler modules.

// The following expression cannot be encoded in Json Schema
const E = Type.RegExp(/<a?:.+?:\d{18}>|\p{Extended_Pictographic}/gu)

Value.Check(E, '♥️♦️♠️♣️') // true

Type.RegExp does enable international character set support options for users. But do still recommend Type.String({ pattern: '...' }) for most cases. For Ajv users, the above can be largely expressed via custom string format.

Hope this helps!
S

from env-schema.

@climba03003 you're right we can close this issue.
At first I thought it was related to how fastify-env would interprete the ajv schema.

My bad on this one.

And thanks @sinclairzx81 for the clarification :)

from env-schema.