Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(@angular/cli): fix test typings #5504

Merged
merged 2 commits into from
Mar 20, 2017
Merged

Conversation

filipesilva
Copy link
Contributor

@filipesilva filipesilva commented Mar 18, 2017

fix(@angular/cli): fix test typings

Our unit test webpack config was erroneously sending in entry points to karma-webpack, who should receive no entry points.

This in turn was hiding errors related to typeRoots lookups.

It was also causing unit tests compilation to behave weirdly: unit test errors would not stop compilation, because other entries would still compile.

This might also have contributed to the overall slowness of unit tests in #5423.

Related to TypeStrong/ts-node#283

Fix #3911
Fix #5332
Fix #5351


fix(@angular/cli): fix error handling on test

Fix #2778
Fix #3424

@filipesilva
Copy link
Contributor Author

There seems to be something else going on here. tsc does need the typeRoots, but we do.

@filipesilva filipesilva force-pushed the fix-test-typings branch 4 times, most recently from eb63b6f to 5ab01b7 Compare March 19, 2017 15:56
@filipesilva filipesilva requested a review from hansl March 19, 2017 15:56
@filipesilva filipesilva force-pushed the fix-test-typings branch 4 times, most recently from 31ece40 to 2d6d4e2 Compare March 19, 2017 16:50
@filipesilva filipesilva force-pushed the fix-test-typings branch 3 times, most recently from 1e72de0 to 055a4b7 Compare March 19, 2017 23:48
Blocked by angular#5500 (fix is included in this PR so that CI will run).

Our unit test webpack config was erroneously sending in entry points to karma-webpack, who should receive no entry points.

This in turn was hiding errors related to typeRoots lookups.

It was also causing unit tests compilation to behave weirdly: unit test errors would not stop compilation, because other entries would still compile.

This might also have contributed to the overall slowness of unit tests in angular#5423.

Related to TypeStrong/ts-node#283

Fix angular#3911
Fix angular#5332
Fix angular#5351
@filipesilva filipesilva force-pushed the fix-test-typings branch 3 times, most recently from 79c68a8 to fd29bfb Compare March 20, 2017 11:15
Copy link
Contributor

@hansl hansl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hansl hansl merged commit 9cda847 into angular:master Mar 20, 2017
@filipesilva filipesilva deleted the fix-test-typings branch March 20, 2017 16:19
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants