Cameron Taggart

Yes, it would be great if we could do this in combination with #110 to have uniquely named overloads. Now accepting design proposals.

One example is property setters. For this ``` fs type [] TlsOptions = abstract host: string option with get, set abstract port: float option with get, set abstract pfx: U2...

For the unions in the functions, building off of a #110 proposal, we could add functions for each unique combination of cases. ``` fs abstract readFileSync: path: U2 * ?options:...

Ah, so the main problem is that ts2fable is generating `obj` for `TypeLiteral`s #93. From node/index.d.ts, the 3 functions are: ``` ts export function readFileSync(path: PathLike | number, options?: {...

Thinking out loud here. How do we solve this case: ``` fs type [] Http2SecureServer = inherit tls.Server type [] Server = inherit net.Server type [] Server = inherit events.EventEmitter...

I'd like to compare the output with: https://github.com/fable-compiler/fable-react-native/blob/master/src/Fable.Import.ReactNative.fs

Thanks for the write-up.

It would be nice to extract out the anonymous `StringEnum` if we can come up with a naming convention that does not have naming conflicts. If I was to make...

This is really a duplicate of #45

Thanks for the report @nojaf, I'll have a look.