You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
There are several breaking changes in the tslint API for integrators that are not documented in the release notes. While typescript helps to find the breaking changes, it would be helpful when the breaking changes are documented in the release notes.
These are the breaking changes I've discoverd when adding support for tslint 5
LintResult.failureCount -> LintResult.errorCount
class Fix -> type Fix = Replacement | Replacement[]
The text was updated successfully, but these errors were encountered:
Hi @egamma, sorry about that -- I've gone ahead and added those breaks to the 5.0.0 release notes. Let us know if there are others. Also, we're here to help and would be happy to review migration PRs for v5 (we use vscode-tslint a lot too!)
Hi @egamma, sorry about that -- I've gone ahead and added those breaks to the 5.0.0 release notes.
Just stumbled upon LintResult.failureCount -> LintResult.errorCount. I just looked at CHANGELOG.md before. Maybe it would be good to have just one source of truth for changelogs? (If you decide to use the release notes I'd keep the CHANGELOG.md thou just to point to the release notes.)
One disadvantage of release notes: they aren't searchable. I found this issue, because I searched for failureCount. CHANGELOG.md would be searched, too.
There are several breaking changes in the tslint API for integrators that are not documented in the release notes. While typescript helps to find the breaking changes, it would be helpful when the breaking changes are documented in the release notes.
These are the breaking changes I've discoverd when adding support for tslint 5
LintResult.failureCount
->LintResult.errorCount
class Fix
->type Fix = Replacement | Replacement[]
The text was updated successfully, but these errors were encountered: