You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm exporting little slices of my types to a type definition to be consumed by plugin authors of my software. I'd like these types to be completely denormalized/fully resolved so I don't have to worry about references or other problems (like some files using node libs).
That's not possible in general, e.g. with recursive types. So I doubt there's a pre-made solution for this; you'd have to think about handling these edge cases firstly.
Alright well I haven't solved it yet as I prefer to use the compiler tools rather than re-implementing a lot of logic. Created to #1346 be more specific.
I'm exporting little slices of my types to a type definition to be consumed by plugin authors of my software. I'd like these types to be completely denormalized/fully resolved so I don't have to worry about references or other problems (like some files using node libs).
Ideal API;
Which would transform something like:
to:
at which point I can print out node B to a d.t.s file without worrying about type A being visible or worrying about including it (in case of imports).
The text was updated successfully, but these errors were encountered: