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

Migrate to a typed language (e.g. TypeScript) #8

Open
jahed opened this issue Aug 9, 2018 · 0 comments
Open

Migrate to a typed language (e.g. TypeScript) #8

jahed opened this issue Aug 9, 2018 · 0 comments

Comments

@jahed
Copy link
Contributor

jahed commented Aug 9, 2018

Due to the core use case of vast-parser being to transform data from one structure to another, a type system will provide a huge benefit.

The main benefit is that the structure of VastResponse can be self-documented and enforced. Right now, that structure isn't entirely obvious.

The other benefit is to auto-generate documentation (by using something like typedoc). Keeping the README up-to-date and accurate by hand isn't easy.

With a type system, it'll also make it easier to move towards a more functional approach. Eventually allowing an application to tree-shake any unused code.

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