Conversation
There was a problem hiding this comment.
Definitely up for more discussions around the TODOs you've got in here, but I like the general idea you're going for. What do you think of calling the directory integration-tests instead of transformedTests? The code already uses dash-casing for its filenames, and I think what these tests really do is test the "whole shebang", but in a faster and easier to work with way than the corpus test that builds external projects.
EDIT: See my comment at the bottom of the review about the ts-patch/TS5 stuff
That's all in addition to, as you said, making it easier for people to contribute tests, both for validation purposes and (I hope!) for submitting with their PRs and bug reports.
| "declaration": false, | ||
| "plugins": [ | ||
| { | ||
| "transform": "typescript-rtti/dist/transformer" |
There was a problem hiding this comment.
set this to "../dist/transformer"
There was a problem hiding this comment.
Works, as is, after the change in package.json
|
Oh wait I see, it's because It really shouldn't. Even if I add TS5 into the subfolder, it still complains. If I install TS5 in the root it works fine. That being said, I think this PR should target 4.9 unless/until the main project upgrades to 5.x. Note that while the transformer supports up to TS 5.1, I left the main devdependency at TS 4.9 since it is the minimum supported, the idea being to help avoid breaking compatibility inadvertently. |
…cript-rtti package
Done so. |
See readme.
Tests, for which the code has type information transformed in. This way, it's much easier to write mass tests for the validator. Just the project setup with some basic examples
i.e.