Ben
Ben
This would probably require some work on the other targets? If this could work on each target it might make sense to contribute the sync version to the haxe std....
Well, most of it is covered by the nodejs target already: https://github.com/HaxeFoundation/hxnodejs/blob/master/src/Sys.hx What would you expect to be in it? All I can think of is a sink for stdout...
I'll add it when your PR is merged/released :)
This seems to be the way to go. > I guess we add an "internal" flag to TypeUtil.className and alike to govern the prefix. Sounds good.
Should it be default though, or only for name clashes? Debugging experience would be slightly nicer when we can keep the class names similar as much as possible. -- Somehow...
There's no setting or anything available. It's hard to see the use case too. Do you have an example setup where this would be required? Maybe a better example project...
`$global.GlobalType` should not be used in type definitions. Not sure how to fix the issue there
All I found so far is this: https://github.com/Swatinem/rollup-plugin-dts It might also be interesting to port the enum types generation back to hxtsdgen: https://github.com/elsassph/hxtsdgen/issues/32#issuecomment-549037318
One of my use cases for genes is (eventually) publishing some generated js code. To have the best interop (and ease documentation) having the same structure is quite useful. Your...
Another option is to produce a warning if you're using dynamicImport but a type from the same module is imported outside of the callback.