-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Add angular@7 cli tests #4524
Add angular@7 cli tests #4524
Conversation
@@ -0,0 +1,13 @@ | |||
# Editor configuration, see http://editorconfig.org |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were there ever changes to a fixture app? I removed .editorconfig in the v6 fixture because I thought it would just apply rules you don't want to apply
But they are re-written by the pre-commit anyway, I guess
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can delete this... didn't even notice it =)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They added this file in the generator of ng new
- I don't know why.
Codecov Report
@@ Coverage Diff @@
## master #4524 +/- ##
=======================================
Coverage 35.58% 35.58%
=======================================
Files 557 557
Lines 6730 6730
Branches 883 883
=======================================
Hits 2395 2395
Misses 3876 3876
Partials 459 459 Continue to review full report at Codecov.
|
After bumping the angular versions something broke in react 🤔 |
Please try merging master |
But it's possible that this is the problem with hoisting I mentioned in #4405 (comment) You've changed some dependencies in project, it affects |
Yep, also mentioned it in #4405 (comment) =) |
…test-2 # Conflicts: # examples/angular-cli/package.json
Friendly reminder: the best way to resolve conflicts in |
TBH, that is what I am doing. If I have conflicts during the merge in |
…test-2 # Conflicts: # yarn.lock
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
That's what I did before I knew about this feature =) |
Wait, you mean I can run yarn with the broken yarn.lock, and it will fix it ? 😵 |
Exactly |
AFAIK |
😱 |
Issue: Add angular@7 to cli tests