Proposal for type validation test runner #667
Conversation
|
cc @robwormald , would like to ask suggestions for output format or any other. |
| console.log('Error : '.red + message); | ||
| console.log(lines[pos.line].gray); | ||
| console.log(_.repeat(' ', pos.character) + '^'); | ||
| console.log(); |
There was a problem hiding this comment.
Yes, that could be way. Will update.
kwonoj
force-pushed
the
chore-typevalidate
branch
from
af7bab9 to
fa0a93c
Compare
|
Small update suggestion from @staltz to use console.error with minor output changes.
|
|
This is interesting. How long does it take to run, on average? (I'll pull it down sometime soon and give it a try, too) |
|
What I did was just small code snippet does not reflect real world cases (having lot of files, or codes) though, it took about a second. For comparison reference, on same system typescript build takes around 14 sec, unit test takes around 2.3 second. |
|
@trxcllnt ... what are your thoughts? |
|
Marked this as blocked while exploring feasibility of migrating unit test cases to typescript based. |
|
@kwonoj I'm going to close this for now since discussion here is dead. We can open a new issue for it to create more discussion, or we can discuss off-line and open an issue when we have some plans outlined. |
|
Agreed, thanks. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
relates to #661
This PR include small code snippet to check basic type definitions as discussed in issue.
There'll be chances of improvement to have additional type detection for verbose output, would like to consider this as starting point.
No actual tests & CI integration included yet.
Output example
