-
Notifications
You must be signed in to change notification settings - Fork 34
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
Should we move to TypeScript? #388
Comments
In short: I'd absolutely support it. Pros:
Cons:
I'd be happy to help, but can't make promises, I'm not sure how much free time I'll have :/. |
Any particular way you want to write it (like C#ish way or more Flow-ish)? We have an experience using TypeScript in our projects and what I see so far — it really matters which features will you use. Sometimes doesn't look like JS and new concepts could lead to some new issues. Also, tooling is matter — to get most of the typescript is it better to use VSCode\Webstorm. But there still could be some problems: for example, we found an issue with tslint using async\await. So for me would be cool to see the way you want to use it (like a guide or so) |
Overall I favor the idea and I think it makes sense since we already support TypeScript through type definition files. Pros:
Cons:
|
Refs #406 |
Yes, we are migrating. |
This is an issue for collecting feedback on whether writing FrintJS source in TypeScript is a good idea or not.
Some questions that I would like everyone to answer:
If all positive:
The text was updated successfully, but these errors were encountered: