Open greenkeeper[bot] opened 7 years ago
Merging #84 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #84 +/- ##
=======================================
Coverage 96.55% 96.55%
=======================================
Files 6 6
Lines 58 58
Branches 3 3
=======================================
Hits 56 56
Partials 2 2
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update f5e3368...ddba1d5. Read the comment docs.
Update to this version instead π
Thanks to @wKoza for code reviews and implementation of "check-semicolon"
.
angular-whitespace: [true, "check-semicolon", "check-interpolation", "check-pipe"]
- Checks if there's whitespace after semicolon, around an expression surrounded by interpolation characters, and after a pipe symbol.
Update to this version instead π
@Pipe
decorator where we use a shorthand syntax for passing properties #399 8e3fafbcheck-pipe
option of angular-whitespace
#365 bef790bThanks to @wKoza for working on the introduced features, bugfixes and code reviews!
Update to this version instead π
Enable the new rule by adding the following line in your tslint.json
config file:
"no-on-prefix-output-name": true
Thanks to @eromano for the rule implementation!
templates-use-public
, no-access-missing-member
, invoke-injectable
and template-to-ng-template
no longer exist. Remove them from your tslint.json
configuration.Update to this version instead π
noOutputOnPrefixRule
and rename it to no-output-on-prefix
. You can now enable it with:"no-output-on-prefix": true
noOutputOnPrefixRule
.Update to this version instead π
angular-whitespace
related to check-semicolon
and check-interpolation
#469 2ef7438Thanks to @sagittarius-rev for the bug fixes!
Update to this version instead π
Thanks to @gbilodeau for NoOutputNamedAfterStandardEventRule
and wKoza for the code reviews!
Version 3.1.0 of codelyzer just got published.
The version 3.1.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 codelyzer. 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
3.1.0New rules
angular-whitespace: [true, 'check-interpolation', 'check-pipe']
- Checks if there's whitespace around an expression surrounded by interpolation characters, and after a pipe symbol.banana-in-box: true
- Checks for proper banana in a box syntax -[(ngModel)]
instead of([ngModel])
.no-negated-async: true
- Enforces(foo | async) === false
, rather than!(foo | async)
, because of the initial falsy value emitted.use-view-encapsulation: true
- Enforces enabled view encapsulation.Special thanks to @wKoza, @GregOnNet and @connor4312 for their contributions.
Features
ViewEncapsulation
#300 509c8d9. Big thanks to @GregOnNet.Fix
*ngFor
#306 36705fcNot 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: