Add script for running tsec#105748
Merged
jrieken merged 1 commit intomicrosoft:masterfrom Sep 1, 2020
Merged
Conversation
Member
|
lgtm - merging |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This PR fixes #105747. It adds a tsec as a devDependency and a "tsec-compile-check" script for running it on the VSCode's codebase.
For now, the added devDependency points to tsec github repository. This should be replaced within a week with an npm package name – as soon as we add tsec to npm.
Usage is very straightforward. After installing the missing dependency, a tsec compile check can be started with:
yarn tsec-compile-checkThe run might take a while (up to 1 minute on an average computer). At the end, there should be several (44 as of now) compilation errors displayed with a fragment of violating code and a source of violation.