Add runtime validation for options #468
Merged
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.
Fixes #467
This uses the libraries ts-interface-builder and ts-interface-checker to codegen
a data structure of the options TS type and then check it on every
transform
invocation.
I tried a few approaches here, including generating JSON schema and then
validating that, but that this seemed to be pretty smooth from a build system
standpoint.
I timed this on 1000 compilations of a large file and any difference was well
within the time variability, so it seems fine to run this type validation on
every
transform
invocation. It could potentially be moved out into a separateroutine if perf is ever an issue, though.