-
Notifications
You must be signed in to change notification settings - Fork 235
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
Support for tslint^5 #281
Comments
Fwiw, I've started taking a stab at refactoring some of the rules to be compatible with tslint^5 Let me know if I should make a PR now or wait till this is more mature |
Thanks for the help! PR sounds good. We should think how to release them. Probably introducing codelyzer@3.0.0 and pushing the features in the current 3.0.0 branches to 4.0.0 sounds reasonable. |
I'll massage the commit based on @ajafff's comments (links below) and make a PR later today |
did not watch out for my previous mistake with tslint. mgechev/codelyzer#281 Will be updated in codelyzer in 3.0.0
tslint v5.1.0 was released. Will you support this version too? |
Since it's a minor release, in case we support 5.0.0 we'll automatically have support for 5.1.0. Over the weekend I'll work on the migration to version 5 and open a PR in the CLI once done. |
The support for tslint@5 just landed in master. I'll publish a new release over the weekend. |
Closing the issue. 3.0.0 should be available tomorrow, followed by PR to the CLI. |
Codelyzer 3.0.0 is published https://www.npmjs.com/package/codelyzer. |
@mgechev Thank you for this! PR for the CLI pending for review angular/angular-cli#6058 |
Also fixes any encountered errors. This only changes the version used for the CLI's development. The project template version of tslint cannot be updated until codelyzer supports the latest version. ([codelyzer tracking issue](mgechev/codelyzer#281))
Also fixes any encountered errors. This only changes the version used for the CLI's development. The project template version of tslint cannot be updated until codelyzer supports the latest version. ([codelyzer tracking issue](mgechev/codelyzer#281))
No description provided.
The text was updated successfully, but these errors were encountered: