Skip to content

fix: Use "any" for types without a primitive mapping

Jay Billings requested to merge next into main

This should result in TypeScript models being generated even when the exact type can't be translated into TypeScript by using the "any" type. It may be more appropriate to use the "unknown" type in the future.

Signed-off-by: Daniel Bluhm

Merge request reports