This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Update dependency tslint to version 4.4.2 #223
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request updates dependency tslint from version 4.3.1 to 4.4.2
Changelog
4.4.2 / 2017-01-26
==================
More descriptive failure message, minor code style fixes
Fixed: #2129
This reverts commit aaa231918ca2a4c386b9a307b4abe1fe9d317918.
4.4.1 / 2017-01-25
==================
4.4.0 / 2017-01-25
==================
This reverts commit 18e760481438404ccc6dc6edef0a6b4bc8e9a9e9.
This reverts commit e6ca41432521a3e5df2780c50478d10f1964a96d.
Fixes Include type definitions for failure fix JSON? palantir/tslint#1788.
Fixes Add a visitNumericLiteral to SyntaxWalker palantir/tslint#2074.
Explicitly call `findConfiguration` before calling `lint` API so that `extends` key is resolved correctly.
Detect trailing whitespace in comments.
Detect trailing whitespace before EOF.
Add fixer.
Fixes: #2049
Fixes Allow --test against a glob pattern of directories palantir/tslint#2064.
It keeps a small blacklist of places functions that return Promises
aren't allowed to be.
Fixes: #2065
This commit can be reverted once tslint drops support for typescript 2.0.10
Fixes #2054
Scanning the whole source file is very fragile, because the grammar is not context free. You had to skip certain ranges, that were known to cause trouble. For example regex literals or template expressions.
This approach is also very fragile, as it didn't cover all cases and has to adopt new grammar as the language adds it.
The new function hands the scanning and parsing off to the parser and only iterates over the tokens of all AST nodes. Skipping ranges is no longer necessary.
Also added deprecation comment to scanAllTokens.
In particular, call out that only trivially inferred types of literals
should be left out, not every type that's inferrable.