The version 3.0.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 @smartive/tslint-config.
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.
rule-set: Add member access as well as function name (#4) (626d1b0)
BREAKING CHANGES
rule-set: This adds member-access as a required rule.
This rule forces the user to add public, private and protected modifiers
to their class members. To migrate, install the new version and use the
given visibility members on classes.
Commits
The new version differs by 1 commits.
626d1b0feat(rule-set): Add member access as well as function name (#4)
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).
greenkeeper[bot]
commented
6 years ago
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 3.0.0 of @smartive/tslint-config was just published.
The version 3.0.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 @smartive/tslint-config.
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.
Release Notes
v3.0.03.0.0 (2018-03-26)
Features
BREAKING CHANGES
member-accessas a required rule.This rule forces the user to add
public,privateandprotectedmodifiersto their class members. To migrate, install the new version and use the
given visibility members on classes.
Commits
The new version differs by 1 commits.
626d1b0feat(rule-set): Add member access as well as function name (#4)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: