Loose string schema
Does arktype have loose string support? though the schema can accept any string, the infered type can be something like
12 Replies
Maybe
type("string").as<Thing>()?there's no such infering from the schema to get that disired result?
I don't really understand what a "loose string" is
well you can try with the
type Thing example above
this works well, but then it's still that we're writing our own typescript type and arktype at the sameBold of you to assume I've got access to my PC (I don't) :)
Have you tried
type.enum("'literal'", "'or'", "'any'", "string")?
enum is for exact value right? which means we're passing the literal value there
and if we add
.or("string"), it still infers as stringSorry, I meant
type.or(xxx, yyy, zzz, aaa)
But yeah, it's likely TS just reduces itit's invalid in arktype, but valid in typescript
When you do
(string & {}) in a union of string literals it allows autocomplete while not rejecting other strings.
I tried a bunch of weird workarounds and the only one I got working was by making union with "string" (type.or("string")) and wrap that is a function that casts the return type.
so
though it is kinda sketchy@TizzySaurus's original suggestion was optimal:
string & {} is just a TypeScript trick to get completions and has no meaning at runtime. The only thing you actually want to validate in that case is string
When a "feature" like (string & {}) has no effect at runtime, a cast is appropriate as there's no meaningful runtime value to derive the type fromnice