arktype
arktype copied to clipboard
arktypeio
TypeScript's 1:1 validator, optimized from editor to runtime
This is for personal tracking purposes for the major tasks left for the beta release. - [x] Finish migrating Problems API - [x] Global/scope/type configs - [ ] Finish integrating...
Currently, since we only populate the snapshots from a single tsVersion, we also only check the primary version for an assertion like `attest({}).type.toString.snap("{}")`. It would be ideal to only populate...
A [Boston TS](https://boston-ts-website.vercel.app/) attendee (please take credit if you see this) suggested this could be optimized using a breadth-first approach to traversal. While changing the traversal pattern would likely incur...
# Request a feature Add `userDefinedContext` (along with `objectPath` and existing `root` and `path`) to validation context and `userDefinedContext` to define it ### 🤷 Motivation Sometimes you may want your...
# Request a feature Add `objectPath` (along with existing `root` and `path`) to validation context ### 🤷 Motivation During validation, you may want to get current `parentNode`, `parentNode.parentNode` and so...
Especially relevant for "===" check for symbols with the same name or objects with the same structure. Not sure if there are other cases where this would come up, but...
# Report a bug ### 🔎 Search Terms Typescript 5.5 ### 🧩 Context - ArkType version: 2.0.0-dev.11 - TypeScript version: 5.4.5, 5.5.0-beta - Other context you think may be relevant...
Currently, because JSON for a cyclic type references only its alias like `$a`, if two scopes had differing definitions for the same cyclic alias, caching could break. Really this should...
Currently unions don't use their discriminators during traversal. Reintegrate these, and ensure that unions of morphs that are not discriminable are errors.
The current transform behavior for cyclic nodes is not robust. I slapped together a ctx with seen and lazy resolutions, but currently `lazilyResolve` is limited to root nodes, whereas to...