Represent `Map`s as records about zod-to-json-schema HOT 6 CLOSED

Done in master

from zod-to-json-schema.

Maps are not handled properly

it is not clear how to represent them

Pick one :)

It doesn't matter that it has a preprocess if it can't be guaranteed to be used all the time.

from zod-to-json-schema.

Pick one :)

Ok, fair.

It doesn't matter that it has a preprocess if it can't be guaranteed to be used all the time.

I'd be fine with an opt-in, since either way we build schema explicitly - maybe we could just have a configuration option?

from zod-to-json-schema.

I ended up using this hack:

const coercedMap = <K extends ZodTypeAny, V extends ZodTypeAny>(
  keySchema: K,
  valueSchema: V,
) =>
  z.preprocess(
  (arg, ctx) =>
      arg === undefined
        ? new Map()
        : new Map(
            Object.entries(arg as {}).map(([key, val]) => [
              keySchema.parse(key, {
                path: [...ctx.path, key, "<key>"],
              }),
              val,
            ]),
          ),
    // For JSON Schemas pretend we are an object rather than a map.
    tweaks.jsonSchemaHack
      ? (z.record(keySchema, valueSchema) as never)
      : z.map(keySchema, valueSchema),
  );

tweaks.jsonSchemaHack is a global that is toggled on when we export schemas, but is off for everything else.

What I'm looking for is to get rid of the tweaks.jsonSchemaHack - if it was possible to just tell zod-to-json-schema I am using z.map but I want it to look like a z.record that would be great.

from zod-to-json-schema.

Sure, wth.

from zod-to-json-schema.

Sweet! Thanks!

from zod-to-json-schema.