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

TypeScript: Update tooling or remove #90

Open
pago opened this issue Jan 13, 2019 · 0 comments
Open

TypeScript: Update tooling or remove #90

pago opened this issue Jan 13, 2019 · 0 comments

Comments

@pago
Copy link
Contributor

pago commented Jan 13, 2019

Explain the problem

Our current TypeScript integration is rather limited and dated. We should decide whether we want to keep using it (in that case: Switch to Babel TypeScript integration + ts-check) or if we consider it to be a failed attempt.

My personal preference would be to double down on TypeScript and to start converting our code base to fully utilize it. Especially a complex project like Melody which involves a parser, compiler and various transforms could benefit from type information and might be more approachable if we have that available.

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

1 participant