Generic minimum and maximum
`.configure` not being applied
.configure
to customize the error messages and it seems like it isn't being applied.
For instance if you put this in the playground, you'll see that the error message is "Password must contain at least one character that isn't a letter or number"
. My expectation is that it would either be 'override problem'
or 'override message'
because that's what I've configured.
Additionally, if I add console.log
statements to the problem
and message
functions it looks like those never run....It is compatible with Nuxt UI?
How to ensure comma delimited set of numbers or fallback to undefined?
Fix Slow Types Warning When Publishing to JSR?
onUndeclaredKey()
Hint for discriminators in union for better error messages?
0|1
& 2|3
)....Discriminated union with union type discriminator gives wrong error messages
Optional union value?
type inference resolves types from scopes to never in union
Standard Schema validation output issues can't be flattened
string < 10 & /some_regex/
and it fails both
I feel like the default should flatten all errors in arktype to match the others behavior, or at least make it configurable?
Or is the intention to just wrap our own StandardSchema around arktype where we flatten if needed?...union of strings & Record as Generic argument
.narrow(...).in doesn't return the original type
.in
to be able to call .toJsonSchema
For the moment I'm using .pipe
but this sounds like a bug...Type.any but with specific scope?
Set object property alias for errors?
branded types are not portable when declaration: true
The inferred type of 'Test' cannot be named without a reference to '.pnpm/@[email protected]/node_modules/@ark/util'. This is likely not portable. A type annotation is necessary.ts(2742)
The inferred type of 'Test' cannot be named without a reference to '.pnpm/@[email protected]/node_modules/@ark/util'. This is likely not portable. A type annotation is necessary.ts(2742)
Is it normal for error messages / potentially behaviour to change depending on jitless?
jitless: true
(due to a bug with jitless that has been fixed) and i noticed that the validation behaviour was different when i set it to jitless: false
. Sadlly i didn't manage to reproduce the different validation behaviour but if you paste this into the web playground
```ts
const formScope = scope({
"form.number": "string.numeric.parse",...Empty string or number
Why ArkType when providing JSON Schema returns nulls as "{"const": null}"?
toJSONSchema
. Problem being that mentioned built-in function returns nulls
from schema in a bit weird format with "const: null" and for example further when I'm using tools to generate openapi it just doesn't work correctly. That wouldn't be that big of a deal if not for types generation from openapi, where all those nulls
are treaded as unknowns
. I've tested both @hey-api/openapi-ts
and openapi-typescript
to generate types and both don't recognize it as null
. For converting from json-schema to openapi I'm using openapi-json-schema
. I would be very thanful if you could help me resolve that....Is there a way to "deep" require a type?