Frontend/chore/typecheck unit tests #1062
Closed
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.
Fixed the typescript errors in tests and changed the
test-ci
script so that CI pipeling fails if tests have typescript errors.This PR has no affect when running
yarn test
locally.Adding
tsc
to thetest
script as suggested in facebook/create-react-app#5626 will not fully work withreact-scripts test
and might cause frustration if you have to wait for the entire source code to be typechecked by tsc when you just want to run a single test. Also it would only run tsc a single time. If no typescript errors have been detected, jest will start in watch mode. Meaning that typescript errors added while test script is already running (and watching for file changes) will still go unnoticed.I've added
tsc
as stand alone script so developers can run it locally withyarn tsc
as a temporary help to check all files for typescript errors.#851