David Blass

Should also allow flat tuple expressions like: ```ts const t = type(["string", "|", "boolean", "|", "number"]) ```

Also consider reintegrating static satisifiability validation, e.g. for `type("string&number")`. This could be useful at least to do shallowly to help with cases like morphs. It was a pain maintaining it...

Our new TypeNode system could support something like this in a fairly straightforward way by implementing multiple input output formats. Something most people probably don't know about ArkType is that...

Thanks, this is definitely useful to keep in mind! The existing `Problems` class is an array subclass that does have a `.summary` prop, but every part of the error message...

@Dimava Good catch, to used to writing AT definitions 😅 Will fix!

Hmm okay, I'll have go dig into this a bit since I haven't worked with these tools. Currently the input type for those options is: ```ts export type MustBeWriter =...

> So it would be the best to only keep the data and let the message parser to compose the message however it wants. To be clear, the data is...

@unional Whoops, my bad! Not so useful if you can't access them😅 I'll be sure those are exposed for the next release, and the rest of this gives me good...

@thelinuxlich Definitely plan to support an output format as well, but haven't actually documented that yet. Would you be willing to create a new issue so we can track compiling...

@ecyrbe mentioned he built a [static JSON Schema parser for TypeMatic](https://github.com/ts-api-spec/typematic)🔥 Would be great if we could integrate somehow so we don't duplicate work in the ecosystem! Let's make sure...