Support for union or discriminatedUnion?

[jackwlee01]

The following code produces a runtime error:

  thing: publicProcedure
    .meta({ openapi: { method: 'GET', path: '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/api/thing' }})
    .input( z.union([
      z.object({ type: z.literal('first'), myVar: z.string() }),
      z.object({ type: z.literal('another'), anotherVar: z.number() }),
      z.object({ type: z.literal('third') }),
    ]))
    .output( z.string() )
    .query(({ ctx }) => "thing" ),

TRPCError: [query.thing] - Input parser must be a ZodObject

Is there any planned support for union or discriminatedUnion?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[levi]

I looked into this. Looks like a non-trivial change since zod-to-json-schema simply returns an anyOf set whenever it sees a union with the openapi3 option.

To properly support OpenAPI3 style discriminators, one would have to either modify zod-to-json-schema to support an openapi3 specific output (which would be a significant change for that package) or perform some pre/post processing in zodSchemaToOpenApiSchemaObject.

I think the latter would be better for this library, specifically. However, I still need to investigate further what a preprocessing or post processing step would look like in practice. Open to ideas!

[ThePaulMcBride]

This would be a great feature. Unions are extremely useful for creating strict contracts and type narrowing. I definitely miss having this ability when working with openapi.

[realjesset]

what happened this support? how can I tackle a discriminatedUnion without using it?

[levi]

I wrote a hacky implementation to start a discussion, but realized that my needs were for nested discriminated unions, which are not supported in the OpenAPI 3 spec. I closed my PR, but someone feel free to take a look at the kernel of the PR and open a new one.

[baptisteArno]

I don't understand the challenge since zod-to-json-schema correctly parses unions? anyOf isn't what we want?

[ntindle]

This is also triggered by z.array()

[popuguytheparrot]

+1

[hoangtrung99]

I cannot use this library just because it lacks this feature. This is a necessary thing, but it seems like the library has not been functioning actively recently, could it be that it has died?