The version 5.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of tslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv5.0.0
๐ฅ Breaking changes
Minimum version of TypeScript version is now 2.1.0 (#2425)
The severity level of rules are now configurable and defaults to severity "error". This affects the output of formatters:
[formatter] msbuild was outputting all failures as "warning".
[formatter] pmd was outputting all failures as priority 1. Now, it uses priority 3 for "error" (default) and priority 4 for "warning"
[formatter] json changed the fix property to now contain either one replacement or an array of replacements (#2403)
tslint:recommended configuration updated with tslint:latest rules & options (#2424)
Removed no-unused-new rule, with logic moved into no-unused-expression (#2269)
no-trailing-whitespace now checks template strings by default. Use the new options ignore-template-strings to restore the old behavior. (#2359)
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 7553d82fca7de667cc867dbfb3af3b1d329c0157 on greenkeeper/tslint-5.0.0 into 8610d8d82244d26d10c82fce192088763c1073a4 on master.
Version 5.0.0 of tslint just got published.
The version 5.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of tslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v5.0.0msbuild
was outputting all failures as "warning".pmd
was outputting all failures as priority 1. Now, it uses priority 3 for "error" (default) and priority 4 for "warning"json
changed thefix
property to now contain either one replacement or an array of replacements (#2403)tslint:recommended
configuration updated withtslint:latest
rules & options (#2424)no-unused-new
rule, with logic moved intono-unused-expression
(#2269)no-trailing-whitespace
now checks template strings by default. Use the new optionsignore-template-strings
to restore the old behavior. (#2359)API breaks for custom rules
Removed method
skip
fromRuleWalker
(#2313)Removed all use of the TypeScript Language Service, use only Program APIs instead (#2235)
This means that some rules that previously worked without the type checker now require it. This includes:
no-unused-variable
no-use-before-declare
This breaks custom rule compilation. If your rule was not using the
ts.LanguageService
APIs, the migration is quite simple:Removed
createFix
. Replacements should be passed directly into addFailure. (#2403)Removed deprecated
scanAllTokens
andskippableTokenAwareRuleWalker
(#2370)[feature] The severity level of rules are now individually configurable. Default severity can also be configured. (#629, #345)
severity
:default
|error | warn | warning | none | off
defaultSeverity
:error | warn | warning | none | off
callable-types
outputs errors andmax-line-length
outputs warnings):[new-rule]
prefer-template
(#2243)[new-rule]
return-undefined
(#2251)[new-rule]
no-reference-import
(#2273)[new-rule]
no-unnecessary-callback-wrapper
(#2249)[new-fixer]
linebreak-style
(#2394)[new-fixer]
eofline
(#2393)Full list of changes
OptionallyTypedRule
, which allows rule authors to write a rule that applies when typing is either enabled or disabled (#2300)prefer-function-over-method
now ignores abstract methods (#2307)arrow-parens
with optionban-single-arg-parens
now correctly handles functions with return type annotation (#2265)prefer-function-over-method
exclude overload signatures (#2315)use-isnan
now applies only to comparison operators (#2317)file-header-rule
now handles single-line comments correctly (#2320)newline-before-return
: fix handling of blank lines between comments (#2321)trailing-comma
No longer enforce trailing commas in type parameters and tuple types (#2236)align
don't fix if it would remove code (#2379)unified-signatures
now recognizes rest parameters (#2342)no-inferrable-types
don't warn for inferrable type on readonly property (#2312)trailing-comma
no longer crashes on new without parentheses (e.g.new Foo
) (#2389)semicolon
Ignore comments when checking for unnecessary semicolon (#2240)semicolon
Don't report unnecessary semicolon when followed by regex literal (#2240)--force
is specified (#2322)--test
now correctly strips single quotes from patterns on windows (#2322)prefer-const
only fix initialized variables (#2219)prefer-const
correctly handle variables shadowed by parameters and catched exceptions (#2219)prefer-const
don't warn if one variable in a for loop initializer can not be const (#2219)prefer-const
handle more cases in destructuring (#2219)no-unused-expression
allow comma separated assignments (#2269)ignore-properties
option ofno-inferrable-types
now also ignores parameter properties (#2312)unified-signatures
now displays line number of the overload to unify if there are more than 2 overloads (#2270)trailing-comma
New checks for CallSignature and NamedExports (#2236)semicolon
New check for export statements, function overloads and shorthand module declaration (#2240)semicolon
Report unnecessary semicolons in classes and in statement position (for option "always" too) (#2240)semicolon
check for semicolon after method overload (#2240)array-type
now considerobject
,undefined
andnever
as simple types, allowingobject
,undefined[]
andnever[]
(#1843)(#2353)align
check statement alignment for all blocks (#2379)align
check parameter alignment for all signatures (#2379)--test
can handle multiple paths at once (#2322)only-arrow-functions
allow functions that usethis
in the body (#2229)--type-check
is used without--project
(#2322)-p
as shorthand for--project
to be consistent withtsc
(#2322)prefer-const
show warnings forvar
(#2219)quotemark
fixer unescapes original quotemark (e.g.'\''
->"'"
) (#2359)no-unused-expression
allow indirect eval(0, eval)("");
(#2269)no-unused-expression
checking for unused new can now use optionallow-fast-null-checks
(#2269)no-unused-expression
find unused comma separated expressions in all locations of the code (#2269)no-unused-expression
find unused expressions inside void expression (#2269)defaultSeverity
with optionserror
,warning
, andoff
. (#2416)no-unused-expression
adds optionallow-tagged-template
to allow tagged templates for side effects (#2269)no-unused-expression
adds optionallow-new
to allownew
without using the new object (#2269)member-access
addsno-public
option (#2247)curly
added optionignore-same-line
(#2334){destructuring: "all"}
to only warn if all variables in a destructuring can be const (#2219)ignore-template-strings
tono-trailing-whitespace
(#2359)array-type
now considerundefined
andnever
as simple types, allowingundefined[]
andnever[]
(#1843)Thanks to our contributors!
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: