-
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
"Could not find implementations for the following rules..." Message after upgrading to v5.0.0-beta.1 #791
Comments
Here are renames that we did:
I'll update the changelog. |
@mgechev , in the meantime, I'll pin this issue. |
mgechev/codelyzer#791 Update "deprication" rule.
Hello @mgechev - did we release the changes? Thanks. |
Yes, this we released over a month ago. Try 5.1.0. |
Is it maybe possible to change the tslint message so that it shows the new key for a deprecated one? |
It has to be like so! |
I second ganqqwerty's request; if the old value has been deprecrated we should at least be informed of the new value. |
* Removed deprecated tslint rule * fix renamed tslint rules mgechev/codelyzer#791 (comment) * align tslint file with current default angular 8 setup file * add lint-fix script to package json * updated polyfills * ng lint --fix run * fixed lint errors so far * added tslint differences * use helpers in tsconfig * tslint for code climate
I've got no idea how to fix my tslint.config now. Based upon @mgechev comment above, many names were changed. But when I updated my tslint, it broke on the new names. Here's what I ended up with that appears to be working. That is until another arbitrary name change breaks my ide. Notice the mismash of old and new settings.
Seriously, can we dispense with this nonsense, and either support both old and new names or provide a migration that renames deprecated settings when updating so that I don't have to spend hours figuring out what happened. I have a job to do, and this kind of thing is a hindrance to my productivity. |
@b2k Thank you. Yours worked. |
A couple of rules were deleted in pull request 2179, but they were actually just renamed and not depricated. Some details: mgechev/codelyzer#519 mgechev/codelyzer#791
A couple of rules were deleted in pull request 2179, but they were actually just renamed and not deprecated. Some details: mgechev/codelyzer#519 mgechev/codelyzer#791
Al ejecutar 'ng lint' salían los siguientes avisos...: Could not find implementations for the following rules specified in the configuration: use-input-property-decorator use-output-property-decorator use-life-cycle-interface Try upgrading TSLint and/or ensuring that you have all necessary custom rules installed. If TSLint was recently upgraded, you may have old rules configured which need to be cleaned up. ... que dejaron de aparecer tras seguir los reemplazos indicados en mgechev/codelyzer#791 (comment)
…cycle-interface`. Fixes a warning in CI. > Could not find implementations for the following rules specified in the configuration: use-life-cycle-interface > Try upgrading TSLint and/or ensuring that you have all necessary custom rules installed. > Lint was recently upgraded, you may have old rules configured which need to be cleaned up. mgechev/codelyzer#791 (comment)
After upgrading from Version 4.5.0 to Version 5.0.0-beta.1 i recieve the following message when linting my files:
In Version 4.5.0 linting works without this message. I also updated tslint to v5.14.0 and Angular to v7.2.9.
I am not sure if thats a bug or what i need to do to get rid of this message.
The used tsconfig.json looks like this:
The text was updated successfully, but these errors were encountered: