The version 0.9.0 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint-plugin-typescript.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 42 commits.
57c0f29Update: explicit-member-accessibility only check *.ts and *.tsx files (Fixes #102) (#104)
b804a7cDocs: Add URL to rule documentation metadata (#105)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling dcb3a0f3bb6bda185ce19d0ba93e2578af39d9f7 on greenkeeper/eslint-plugin-typescript-0.9.0 into def5afd3fdf3958d57648a66e14a37558a67718e on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 0.9.0 of eslint-plugin-typescript was just published.
The version 0.9.0 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint-plugin-typescript.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 42 commits.
57c0f29
Update: explicit-member-accessibility only check *.ts and *.tsx files (Fixes #102) (#104)
b804a7c
Docs: Add URL to rule documentation metadata (#105)
7d6d7e1
New: add explicit-function-return-type rule (#103)
bbce3df
Fix: Allow digits in PascalCase symbols (#98)
3cb9db8
Breaking: Support updated TSNodes (fixes #74) (#100)
ddec16f
Update: refactor tests (fixes #81) (#87)
c2f6451
Test: type-annotation-spacing: keyof considered like arrow (#91)
bbfb878
Chore: Publish version 0.8.1 to npm
12220cc
Chore: Update prettier and pin the version (#94)
3284af4
Fix: Mark call expression type parameters as used (#89)
29bd53c
Fix: Mark qualified name type annotations as used (#88)
5e3999d
Fix: Destructured param type annotation not marked used (fixes #82) (#84)
2b197fd
Fix: Handles type spacing on TSParenthesizedType expressions (fixes #79) (#80)
45cd23e
Fix: no-triple-slash-reference (fixes #75)
485254b
Chore: Publish version 0.8.0 to npm
There are 42 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: