Migrating causes null to now be generated as unknown #1960
-
hey, I am migrating from version 0.48.2 to 0.66.4, and have it working fine except for one thing - Here is an example of the types that have been changed:
Right now it isn't feasible to go through the codebase and refactor to use unknown instead of null, is there a way I can get the types to generate how they used to (e.g. This is the current config:
|
Beta Was this translation helpful? Give feedback.
Answered by
henry-encord
Apr 18, 2025
Replies: 1 comment
-
Fixed: The solution to this is to use openapi 3.1.0+ |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
henry-encord
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fixed:
The solution to this is to use openapi 3.1.0+