[WIP] Refactoring vtk.js internals into Typescript #2459
+2,507
−274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
There has been interest to use Typescript internally in vtk.js, rather than just specifying the external API. Because of the exploratory nature of this MR, it will remain in draft form for now and serve as a starting point for discussion. Once interested parties are satisfied with the approach, we can begin incrementally converting parts of the codebase into typescript as needed.
An overview of what this MR contains (will be updated):
macros.ts
OutlineFilter
ClassHierarchy
Some notes that can serve as points of discussion:
*.ts
files. If we start incrementally refactoring into using typescript fully, we will begin running prettier over typescript files. I will leave it open to discussion whether we should prettify*.d.ts
files.@jourdain @finetjul @daker @FezVrasta