Skip to content

TypeScript support. Doc comment. #690

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

Open
infacto opened this issue May 19, 2020 · 2 comments
Open

TypeScript support. Doc comment. #690

infacto opened this issue May 19, 2020 · 2 comments

Comments

@infacto
Copy link

infacto commented May 19, 2020

Don't scare ... just consider to define types. There are multiple ways.
Doc comments are useful with or without TypeScript. Definition files (*.d.ts) can be generated from this comments and the current source code. Or we could move to TypeScript. Ideas are welcome.

Current Alternative
DefinitelyTyped
Types from @types are mostly a gambling game. Because in most cases they are not synchronized and hand crafted. And you have one more dependency. I would prefer a build-in solution. Many libraries already have this. It's optional and separated. It will not blow up the build size.

@kn0wn
Copy link
Contributor

kn0wn commented Jul 27, 2020

It was inevitable this was going to come up. I do support our TypeScript overlords, however due to the current engine architecture, it would need a complete re-write to get it working properly. I'll tag it for now for consideration when the next major release is in the works.

@Ridvanovskyy
Copy link

It was inevitable this was going to come up. I do support our TypeScript overlords, however due to the current engine architecture, it would need a complete re-write to get it working properly. I'll tag it for now for consideration when the next major release is in the works.

Is it possible to participate in this?

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

No branches or pull requests

3 participants