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.

Sign up for GitHub

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

Jump to bottom

Generic properties could be created as their own imports #1

Open
maxstralin opened this issue Jul 14, 2019 · 1 comment
Open

Generic properties could be created as their own imports #1

maxstralin opened this issue Jul 14, 2019 · 1 comment
Assignees
@maxstralin
Labels
enhancement New feature or request

Comments

@maxstralin
Copy link
Owner

Current behaviour serialises them straight into the JS file. Another option, which should be opt-in, could be to create a separate JS class for every found version of the generic class.

E.g. new Generic<string>() and new Generic<int>() could create Generic_string.js and Generic_int.js
@maxstralin maxstralin self-assigned this Jul 14, 2019
@maxstralin maxstralin added the enhancement New feature or request label Jul 14, 2019
@maxstralin
Copy link
Owner Author

Does this make sense for Javascript or is it better to only to it for Typescript (#13)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maxstralin maxstralin

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maxstralin