Skip to content

Conversation

@cyrilletuzi
Copy link
Contributor

@cexbrayat
Copy link
Member

Fixes #8768

filipesilva
filipesilva previously approved these changes Dec 7, 2017
@filipesilva
Copy link
Contributor

LGTM, was just putting up a PR for this right now. Unsure what's happening with CI, looking into it.

@cyrilletuzi
Copy link
Contributor Author

The PR was done before #8765 was fixed, maybe the source of CI error ?

@Brocco
Copy link
Contributor

Brocco commented Dec 7, 2017

@cyrilletuzi Can you please rebase this PR? There have been a few fixes since you created your PR. Thanks!

fix(@angular/cli): set tslint 5 to emit warnings

cli 1.1.0 upgraded to tslint 5, but tslint 5 is now raising errors by default, instead of warnings previously, and it's very confusing (lint errors can't be on the same level as syntax errors).
@cyrilletuzi
Copy link
Contributor Author

Sorry, I had to redo this in #8792

Don't even know how the last operation has been possible, so I've started from start to clean my git history.

@cyrilletuzi cyrilletuzi closed this Dec 7, 2017
@JinsPeter
Copy link

JinsPeter commented Dec 11, 2017

When can npm install @angular/compiler-cli@5.1.0 reflect this warning fix

@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 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants