greenkeeper[bot]
commented
7 years ago Version 5.1.0 just got published.
Update to this version instead 🚀
Release Notes
v5.1.0- [new-rule]
no-invalid-template-strings(#2332) - [new-rule]
no-sparse-arrays(#2407) - [new-rule-option]
no-void-expression: addsignore-arrow-function-shorthand(#2445) - [api]
tslint:allconfiguration (#2417) - [bugfix] In tslint:recommended move
no-reference-importfromjsRulestorules(#2441) - [bugfix]
no-unnecessary-callback-wrapper: only check if callback is identifier, allow all other expressions (#2510) - [bugfix]
member-access: Skip index signature, it can not have an access modifier (#2437) - [bugfix]
restrict-plus-operandsfixes regression where every assignment and comparison was checked (#2454) - [bugfix]
no-unnecessary-callback-wrapper: allow async wrapper function (#2510) - [bugfix]
prefer-for-of: No error ifdeleteis used (#2458) - [bugfix]
radix: don't warn for missing radix on method calls (#2352) - [bugfix]
no-use-before-declare: Handle symbol with empty declarations list. (#2436) - [bugfix]
strict-type-predicates: Check for construct signatures inisFunction. (#2479) - [enhancement]
strict-boolean-expressions: When--strictNullChecksis turned off,allow-null-unionandallow-undefined-unionturn off "always truthy" errors. (#2373) - [enhancement]
radix: added check for global.parseInt and window.parseInt (#2352) - [enhancement]
arrow-return-shorthand: Improve failure message when return expression is an object literal (#2466)
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.0msbuildwas outputting all failures as "warning".pmdwas outputting all failures as priority 1. Now, it uses priority 3 for "error" (default) and priority 4 for "warning"jsonchanged thefixproperty to now contain either one replacement or an array of replacements (#2403)tslint:recommendedconfiguration updated withtslint:latestrules & options (#2424)no-unused-newrule, with logic moved intono-unused-expression(#2269)no-trailing-whitespacenow checks template strings by default. Use the new optionsignore-template-stringsto restore the old behavior. (#2359)API breaks for custom rules
Removed method
skipfromRuleWalker(#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-variableno-use-before-declareThis breaks custom rule compilation. If your rule was not using the
ts.LanguageServiceAPIs, the migration is quite simple:Removed
createFix. Replacements should be passed directly into addFailure. (#2403)Removed deprecated
scanAllTokensandskippableTokenAwareRuleWalker(#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 | offdefaultSeverity:error | warn | warning | none | off{ "extends": "tslint:latest", "rules": { "callable-types": true, "max-line-length": [true, 140] } }callable-typesoutputs errors andmax-line-lengthoutputs warnings):{ "extends": "tslint:latest", "defaultSeverity": "error", "rules": { "callable-types": true, "max-line-length": { "options": 140, "severity": "warning" } } }[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-methodnow ignores abstract methods (#2307)arrow-parenswith optionban-single-arg-parensnow correctly handles functions with return type annotation (#2265)prefer-function-over-methodexclude overload signatures (#2315)use-isnannow applies only to comparison operators (#2317)file-header-rulenow handles single-line comments correctly (#2320)newline-before-return: fix handling of blank lines between comments (#2321)trailing-commaNo longer enforce trailing commas in type parameters and tuple types (#2236)aligndon't fix if it would remove code (#2379)unified-signaturesnow recognizes rest parameters (#2342)no-inferrable-typesdon't warn for inferrable type on readonly property (#2312)trailing-commano longer crashes on new without parentheses (e.g.new Foo) (#2389)semicolonIgnore comments when checking for unnecessary semicolon (#2240)semicolonDon't report unnecessary semicolon when followed by regex literal (#2240)--forceis specified (#2322)--testnow correctly strips single quotes from patterns on windows (#2322)prefer-constonly fix initialized variables (#2219)prefer-constcorrectly handle variables shadowed by parameters and catched exceptions (#2219)prefer-constdon't warn if one variable in a for loop initializer can not be const (#2219)prefer-consthandle more cases in destructuring (#2219)no-unused-expressionallow comma separated assignments (#2269)ignore-propertiesoption ofno-inferrable-typesnow also ignores parameter properties (#2312)unified-signaturesnow displays line number of the overload to unify if there are more than 2 overloads (#2270)trailing-commaNew checks for CallSignature and NamedExports (#2236)semicolonNew check for export statements, function overloads and shorthand module declaration (#2240)semicolonReport unnecessary semicolons in classes and in statement position (for option "always" too) (#2240)semicoloncheck for semicolon after method overload (#2240)array-typenow considerobject,undefinedandneveras simple types, allowingobject,undefined[]andnever[](#1843)(#2353)aligncheck statement alignment for all blocks (#2379)aligncheck parameter alignment for all signatures (#2379)--testcan handle multiple paths at once (#2322)only-arrow-functionsallow functions that usethisin the body (#2229)--type-checkis used without--project(#2322)-pas shorthand for--projectto be consistent withtsc(#2322)prefer-constshow warnings forvar(#2219)quotemarkfixer unescapes original quotemark (e.g.'\''->"'") (#2359)no-unused-expressionallow indirect eval(0, eval)("");(#2269)no-unused-expressionchecking for unused new can now use optionallow-fast-null-checks(#2269)no-unused-expressionfind unused comma separated expressions in all locations of the code (#2269)no-unused-expressionfind unused expressions inside void expression (#2269)defaultSeveritywith optionserror,warning, andoff. (#2416)no-unused-expressionadds optionallow-tagged-templateto allow tagged templates for side effects (#2269)no-unused-expressionadds optionallow-newto allownewwithout using the new object (#2269)member-accessaddsno-publicoption (#2247)curlyadded optionignore-same-line(#2334){destructuring: "all"}to only warn if all variables in a destructuring can be const (#2219)ignore-template-stringstono-trailing-whitespace(#2359)array-typenow considerundefinedandneveras 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: