Bobakanoosh Comments - Answer Overflow

Bobakanoosh

Explore posts from servers

NNuxt CDCloudflare Developers SSolidJS Aarktype DTDrizzle Team

Posts Comments

Aarktype

•Created by Bobakanoosh on 3/22/2025 in #questions

Passing schemas to functions that are piped

Appreciate the response thanks!

4 replies

Aarktype

•Created by Bobakanoosh on 3/13/2025 in #questions

Type instantiation is excessively deep and possibly infinite

Ah well the thing is I need to be able to call the events from a single object so that as unvalidated events come in I can just validate with one easy call. I'll just do the scope unions for now since it would be just as much work to manually add the event types to some other list for my purpose. Is that union helper on a branch somewhere or a ticket so I can track it?

13 replies

Aarktype

•Created by Bobakanoosh on 3/13/2025 in #questions

Type instantiation is excessively deep and possibly infinite

Hmm. Kinda annoying to maintain thats unfortunate - planning on having tons of these. Maybe I'll try to restructure out of a scope, the only reason I had them like that was to be able to do module.event()

13 replies

Aarktype

•Created by Bobakanoosh on 3/13/2025 in #questions

Type instantiation is excessively deep and possibly infinite

export const test = scope({
    event1: "a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | p | q | r | s | t | u | v",
    event2: "w | x | y",
    "event": "event1 | event2",
    a: {
        type: "'a'",
        content: "null",
    },

export const test = scope({
    event1: "a | b | c | d | e | f | g | h | i | j | k | l | m | n | o | p | q | r | s | t | u | v",
    event2: "w | x | y",
    "event": "event1 | event2",
    a: {
        type: "'a'",
        content: "null",
    },

Basically this?

13 replies

Aarktype

•Created by Bobakanoosh on 2/19/2025 in #questions

Early codependent field validation

This is the aforementioned solution of narrowing directly on the dependent field. Probably the best solution I’ve got, though not ideal due to root being unknown and having to validate it myself.

const PasswordSchema = type({
  password: "string > 1",
  confirmPassword: type("string > 1").narrow((details, ctx) => {
    const root = typeof ctx.root === "object" ? (ctx.root as Record<string, unknown>) : null
    if (root && root.password !== root.confirmPassword) {
      ctx.reject({
        expected: "identical to password",
        actual: "",
        relativePath: ["confirmPassword"],
      })
    }

    return !ctx.hasError()
  }),
})

const FormArktype = type({
  "...": PasswordSchema,
  email: "string.email",
})

const arkResult = FormArktype({ email: "test", password: "2345", confirmPassword: "12" })
if (arkResult instanceof type.errors) {
  console.log(arkResult.summary)
}

const PasswordSchema = type({
  password: "string > 1",
  confirmPassword: type("string > 1").narrow((details, ctx) => {
    const root = typeof ctx.root === "object" ? (ctx.root as Record<string, unknown>) : null
    if (root && root.password !== root.confirmPassword) {
      ctx.reject({
        expected: "identical to password",
        actual: "",
        relativePath: ["confirmPassword"],
      })
    }

    return !ctx.hasError()
  }),
})

const FormArktype = type({
  "...": PasswordSchema,
  email: "string.email",
})

const arkResult = FormArktype({ email: "test", password: "2345", confirmPassword: "12" })
if (arkResult instanceof type.errors) {
  console.log(arkResult.summary)
}

4 replies

Aarktype

•Created by Bobakanoosh on 2/19/2025 in #questions

Early codependent field validation

This works but not really ideal, especially in the case of a more complex schema

const PasswordSchema = type({
  password: "string > 1",
  confirm: "string > 1",
}).narrow((details, ctx) => {
  if (details.password !== details.confirm) {
    ctx.reject({
      expected: "identical to password",
      actual: "",
      relativePath: ["confirm"],
    })
  }

  return !ctx.hasError()
})

const FormArktype = type({
  email: "string.email",
  password: PasswordSchema,
}).pipe((v) => {
  return {
    ...v,
    ...v.password,
  }
})

const arkResult = FormArktype({ email: "[email protected]", password: { password: "2345", confirm: "2345" } })
if (arkResult instanceof type.errors) {
  console.log(arkResult.summary)
} else {
  console.log(arkResult)
}

const PasswordSchema = type({
  password: "string > 1",
  confirm: "string > 1",
}).narrow((details, ctx) => {
  if (details.password !== details.confirm) {
    ctx.reject({
      expected: "identical to password",
      actual: "",
      relativePath: ["confirm"],
    })
  }

  return !ctx.hasError()
})

const FormArktype = type({
  email: "string.email",
  password: PasswordSchema,
}).pipe((v) => {
  return {
    ...v,
    ...v.password,
  }
})

const arkResult = FormArktype({ email: "[email protected]", password: { password: "2345", confirm: "2345" } })
if (arkResult instanceof type.errors) {
  console.log(arkResult.summary)
} else {
  console.log(arkResult)
}

4 replies

Aarktype

•Created by Bobakanoosh on 2/19/2025 in #questions

Early codependent field validation

Was hoping I could do something like this:

const PasswordSchema = type({
  password: "string > 1",
  confirm: "string > 1",
}).narrow((details, ctx) => {
  if (details.password !== details.confirm) {
    ctx.reject({
      expected: "identical to password",
      actual: "",
      relativePath: ["confirm"],
    })
  }

  return !ctx.hasError()
})

const FormArktype = type({
"...": PasswordSchema,
  email: "string.email",
})

const PasswordSchema = type({
  password: "string > 1",
  confirm: "string > 1",
}).narrow((details, ctx) => {
  if (details.password !== details.confirm) {
    ctx.reject({
      expected: "identical to password",
      actual: "",
      relativePath: ["confirm"],
    })
  }

  return !ctx.hasError()
})

const FormArktype = type({
"...": PasswordSchema,
  email: "string.email",
})

4 replies

Aarktype

•Created by Bobakanoosh on 1/30/2025 in #questions

Easier way to chain off of string.integer.parse?

I think i saw a diff example that was .to. and i tried that and saw nothing useful to chain off that

9 replies

Aarktype

•Created by Bobakanoosh on 1/30/2025 in #questions

Easier way to chain off of string.integer.parse?

😂 not completely convinced its not true..

9 replies

Aarktype

•Created by Bobakanoosh on 1/30/2025 in #questions

Easier way to chain off of string.integer.parse?

thanks!

9 replies

Aarktype

•Created by Bobakanoosh on 1/30/2025 in #questions

Easier way to chain off of string.integer.parse?

I SWEAR i tried that 😭 😭

9 replies

Aarktype

•Created by Maxzilla on 1/29/2025 in #questions

Zod "parity"? (nanoid, emoji,...)

Beautiful, thanks!

15 replies

Aarktype

•Created by Maxzilla on 1/29/2025 in #questions

Zod "parity"? (nanoid, emoji,...)

So there’s no pitfall/repercussions of using a global scope for that purpose? Just wanting to make sure if I go that route I’m not gonna be 3 months down the road and realize some validation isn’t gonna work because I’m using that global scope. Maybe a paranoid thought

15 replies

Aarktype

•Created by Maxzilla on 1/29/2025 in #questions

Zod "parity"? (nanoid, emoji,...)

Awesome, I find some libraries are opinionated and it’s easier to follow those opinions rather than fight them, so was just checking.

15 replies

Aarktype

•Created by Maxzilla on 1/29/2025 in #questions

Zod "parity"? (nanoid, emoji,...)

@ArkDavid so is your recommendation to have one big global scope that all schemas use, which defines custom types, as opposed to creating types and reusing those? Ex:

const {type } = scope({
    "string.emoji": arkType("string").narrow((str) => /* Placeholder */ true)
})

const stringEmoji = arkType("string").narrow((str) => /* Placeholder */ true)

const someSchema = type({
    input: stringEmoji,
    output: "string.emoji",
})

const {type } = scope({
    "string.emoji": arkType("string").narrow((str) => /* Placeholder */ true)
})

const stringEmoji = arkType("string").narrow((str) => /* Placeholder */ true)

const someSchema = type({
    input: stringEmoji,
    output: "string.emoji",
})