-
Notifications
You must be signed in to change notification settings - Fork 0
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
An in-range update of tslint is breaking the build 🚨 #16
Comments
Version 5.4.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.4.3🛠 Bugfixes
|
Version 5.5.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.5.0Editor's note: This release features an important bugfix for overlapping fixes when using 🎉 New rules and options
🛠 Bugfixes & enhancements
Thanks to our contributors!
|
Version 5.6.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.6.0🎉 New rules, options, and fixers
🛠 Bugfixes & enhancements
Thanks to our contributors!
|
Version 5.7.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.7.0🎉 New rules, options, and fixers
🛠 Bugfixes & enhancements
Thanks to our contributors!
|
Version 5.8.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.8.0
|
Version 5.9.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.9.0
|
Version 5.9.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.9.1🛠 Bugfixes |
Version 5.4.0 of tslint just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
v5.4.0⭐️ Non-breaking API changes
--type-check
CLI option now only enables checking for compiler errors before linting. It is no longer required to enable rules that use the type checker -- only need to supply--project
now.🎉 New rules, options, and fixers
switch-final-break
(#2804)use-default-type-parameter
(#2253)binary-expression-operand-order
(#2805)ban
new options format: allows to specify an optional explanation message for function bans, banning nested methods and using a wildcard for object of a method ban (#2547)no-duplicate-variable
addscheck-parameters
option to check if variable has the same name as a parameter (#2597)curly
: "as-needed" option (#2842)no-unbound-method
add option"ignore-static"
(#2751)strict-boolean-expressions
addsallow-boolean-or-undefined
(#2820)object-literal-shorthand
can fix longhand methods (#2558)🛠 Bugfixes & enhancements
prefer-object-spread
allows constructor, function and method calls and more as first argument toObject.assign
(#2828)no-unbound-method
walker skips past the parent if it is a cast or parenthesized expression (#2838)object-literal-shorthand
: fixed suggestion for generator functions (#2558)no-unused-variable
rule on Windows (#2819)tslint --project
ifallowJs
is set in tsconfig.json (#2823)align
with option"members"
: check members of class expressions; don't check semicolons in classes (#2668)no-inferred-empty-object-type
: fix stack overflow (#2762)semicolon
: don't warn about unnecesary semicolon when it is actually needed, e.g. when followed by type assertion or template string (#2655)space-before-function-paren
: Ignore async arrow function with no parentheses (#2833)no-unsafe-any
: Don't fail oncontinue label;
(#2830)no-unbound-method
: Allow unbound method to be used as a condition (#2834)no-unsafe-any
: Allow to switch on a value of typeany
(#2836)no-unsafe-any
: Don't markdeclare global {}
as an unsafe any. (#2839)indent
now checks indentation of expressions inside template strings (#2826)--project
(or-p
) enables rules that require the type checker.--type-check
only checks for errors before linting is no longer required (#2773)deprecation
: error message includes deprecation text if available (#2748)cyclomatic-complexity
: Don't count empty switch case(#2743)strict-boolean-expressions
: Allowany
, andtrue
andfalse
literal types (#2758)no-floating-promises
: Allow 'promise.catch()' (#2774)comment-format
no longer excludes comments with triple slash from linting except/// <reference path="..."/>
(#2616)prefer-object-spread
: lint more locations where return value is used. (#2828)semicolon
: option"never"
is now spec compliant (#2655)object-literal-shorthand
handles async functions correctly (#2558)--test
CLI option: allow passing path to tslint.json (#2784)strict-type-predicates
: warn if strictNullChecks is not enabled (#2786)Thanks to our contributors!
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: