Open safaci2000 opened 1 week ago
The workaround for this issue is to first generate schema A, then customize the generator for schema B to use the enum model type from schema A.
Okay, thanks. That's good to know. It's not my favorite, since I can't really wipe the generated output and re-create without some code editing, but I'll take it.
I still think at some point having a way to run the jet generator where it loads all known schemas would make Jet a lot more powerful, plus it would be aware of all the given data types.
Describe the bug If you have a datatype defined in Schema A and need to reference it in Schema B, Jet code gen seems to be unable to determine where the type is defined.
The generated code is then confused.
Expected behavior I would expect the generated code to compile