Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transiton into Typescript's external modules #38

Open
kskalski opened this issue Jul 19, 2019 · 0 comments
Open

Transiton into Typescript's external modules #38

kskalski opened this issue Jul 19, 2019 · 0 comments

Comments

@kskalski
Copy link
Contributor

Currently generated code and mscorlib assume they will be used as "internal modules", which is nowadays discouraged / hard to use in new Typescript code:

  • reference to mscorlib is done through ///
  • generated classes are not exported

Such modules seems to be impossible to consume using "import" statements.
It would be nice to have an command line switch to make the generated code export its classes. Ideally mscorlib should albo be exporting its classes (and then generated code would consume them by importing them first), but that would break compatibility with old generated code, which uses ///<reference.. to mscorlib.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant