arktype•10mo ago

standard schema conforming schema in openauth not working seemingly exclusively with arktype?

i'm using the openauth library which is supposed to support standard schema for

subjects

subjects

definition.

i get typesafe output with zod, and the docs use valibot so i assume those 2 work

though with arktype i just get a generic

v1.StandardSchema<unknown, unknown>

v1.StandardSchema<unknown, unknown>

type on the resulting object. with zod i get

z.ZodObject<{
    id: z.ZodString;
}, "strip", z.ZodTypeAny, {
    id: string;
}, {
    id: string;
}>

z.ZodObject<{
    id: z.ZodString;
}, "strip", z.ZodTypeAny, {
    id: string;
}, {
    id: string;
}>

initially i thought this is an issue with openauth, but considering there's this standard schema, and i'm only seeing the issue on arktype i thought i'd come here first, perhaps there's an obvious mistake i'm making? this is the code

export const subjects = createSubjects({
  user: type({ id: type.string }), // arktype
  other_user: z.object({ id: z.string() }), // zod
});

export const subjects = createSubjects({
  user: type({ id: type.string }), // arktype
  other_user: z.object({ id: z.string() }), // zod
});

the link to openauth at the start of the message goes to the subjects part in question

Jjack i'm using the [openauth](https://openauth.js.org/docs/subject/) library which is...

ssalbdivad•3/11/25, 4:31 AM

Is this with arktype 2.1+?

jackOP•3/11/25, 4:33 AM

2.0.4, updating now. was this a known issue?

Jjack 2.0.4, updating now. was this a known issue?

ssalbdivad•3/11/25, 4:34 AM

Yeah, essentially in some contexts where AT was wrapped it would be not be inferred correctly due to some quirks of TS and .

With

2.0.4

2.0.4

, it probably works if you don't inline the definition like:

With 2.1+ it should work either way

jackOP•3/11/25, 4:41 AM

sweet, works with the updated version (i also tried the alternative ^ and it did work too, but i like the inline

)

jackOP•3/11/25, 4:41 AM

thanks!