19 replies

Limitations of `S.TemplateLiteral` Schema Support and the Case for Broader Transform Compatibility

Why does

S.TemplateLiteral

S.TemplateLiteral

have a special whitelisted list of schemas that it supports? It limits the ability to apply transforms to the templated data.

For example,

S.Number

S.Number

is seemingly whitelisted & special cased to work within

S.TemplateLiteral

S.TemplateLiteral

, where the more ergonomic and intuitive choice (IMHO) would be

S.NumberFromString

S.NumberFromString

. And even if we hard-code support for other common transforms such as

DateFromString

DateFromString

BooleanFromString

BooleanFromString

etc into

S.TemplateLiteral

S.TemplateLiteral

, that still doesn't help with user-land transforms.

So given all that, why not make

S.TemplateLiteral

S.TemplateLiteral

support any schemas whose encoded side is

string

string

(or inherits from

string

string

so we support literals/unions)?