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
This is just a note...
I'm looking at writing a TypeScript declaration file generator.
I noticed that GenBase has a bunch of abstract methods like WriteNewArray, WriteListStorageInit, WriteCall etc. Since TypeScript declaration files don't contain method implementations, a GenTsDecls class would have to implement these methods as no-ops. Not a huge deal, but what do you think, should we extract an interface from GenBase so that GenTsDecls and anything like it (I also use Flowtype for some JS projects 🙃) doesn't have to implement a bunch of irrelevant abstract methods?
The text was updated successfully, but these errors were encountered:
Actually nevermind. I might as well just leave stubs that throw NotImplementedException in case we decide to implement full TS source code generation in the future.
actually I ended up just inheriting GenJs for now, so that I can share some of the code for identifier case and so that I can output the correct enum value initializers.
This is just a note...
I'm looking at writing a TypeScript declaration file generator.
I noticed that
GenBase
has a bunch of abstract methods likeWriteNewArray
,WriteListStorageInit
,WriteCall
etc. Since TypeScript declaration files don't contain method implementations, aGenTsDecls
class would have to implement these methods as no-ops. Not a huge deal, but what do you think, should we extract an interface fromGenBase
so thatGenTsDecls
and anything like it (I also use Flowtype for some JS projects 🙃) doesn't have to implement a bunch of irrelevant abstract methods?The text was updated successfully, but these errors were encountered: