Alexander Mattoni

This is awesome, can't wait for this to be merged.

Also commenting in support of this PR @fdehau. Any chance this gets merged soon?

I agree, OpenAPI 3.1 has been out for awhile now, and a type array is the defacto way to handle nullable values. Can this be bumped up in priority?

Any chance this can be bumped up now that ogen is at v1.0.0? I've updated all my specs to 3.1.0 and would like to avoid down-versioning if possible, and ogen...

I see, I understood it as, no other discriminated type can have all the same fields, not that the summary of them cannot appear across multiple different types. Is it...

Is it incorrect to have `{ "type": ["string", "null], "enum": ["a", "b"] }` ? Because I'm getting this in 6.7.5, where anything with a type of string/null and enum is...

Same issue here. Getting a lot of undefined errors around the useMotionConfig() hook.

As of 2.1.0, the types exported from that path (`DefinitionsFromApi, OverrideResultType `) are all resolving to the type "never" and my overrides that worked pre-2.0 are no longer working.

 Those types don't exist at the 'normal' entry point :(

Got it, just figured that out as you commented :) works fine from the new path!