Generation Of Sub-Types

[metasophiea]

Here there!

Lets say I have a struct like this

SomeStruct { thing: usize, anotherThing: CoolEnum }

and I annotate it correctly so that the typescript bindings are generated as we would expect. "CoolEnum" also has the correct annotations, but is being imported from another crate. In this situation, I've found that the "SomeStruct.ts" file contains a line to import the "CoolEnum" type, but the "CoolEnum.ts" itself isn't generated. For that I need to go over to the crate that has "CoolEnum" and transport the typescript file myself.

I can understand why, but is there perhaps an option I'm missing somewhere where I can ask that the system generate typescript files for all the types used within a type?

[siefkenj]

I'm having this exact issue. If the types are declared in another module, even with #[derive(TS)], it seems they won't export.

[NyxCode]

In an other module, or in an other crate?

[siefkenj]

Sorry, in a separate crate.

[escritorio-gustavo]

If CoolEnum is from another crate and doesn't implement TS this is not gonna work, as all fields must implement TS for #[derive(TS)] to work.

Of course, due to Rust's orphan rule you cannot do impl TS for CoolEnum yourself, which is unfortunate.

Thankfully a solution is being worked on! Keep an eye on #113 and its related PR #174

[escritorio-gustavo]

Solved as of #218