Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency codelyzer to v6 #35

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 19, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
codelyzer 2.1.1 -> 6.0.2 age adoption passing confidence
codelyzer ~1.0.0-beta.3 -> ~6.0.0 age adoption passing confidence

Release Notes

mgechev/codelyzer (codelyzer)

v6.0.1

v6.0.0

Bug Fixes

v5.2.2

Compare Source

v5.2.1

Compare Source

v5.2.0

Compare Source

Bug Fixes
Features
5.1.2 (2019-09-26)
Bug Fixes
5.1.1 (2019-09-19)
Bug Fixes

v5.1.2

Compare Source

v5.1.1

Compare Source

v5.1.0

Compare Source

Bug Fixes
  • rule: 'contextual-decorator' - decorators with arguments, accessors and some missing decorators not being handled (#​798) (efbcb69)
  • rule: template-banana-in-box regex failing in some environments (#​820) (3b82574)
Features

5.0.1 (2019-04-25)

Bug Fixes
  • rule: detect trackBy function when ngFor spans multiple lines (#​813) (2260dfd)
  • rule: template-accessibility-label-for not recognizing options and interpolated values (#​812) (1fb5d8a)

v5.0.1

Compare Source

Bug Fixes
  • rule: detect trackBy function when ngFor spans multiple lines (#​813) (2260dfd)
  • rule: template-accessibility-label-for not recognizing options and interpolated values (#​812) (1fb5d8a)

v5.0.0

Compare Source

BREAKING CHANGES

Angular CLI will automatically migrate your projects to reflect the latest config.

  • contextual-life-cycle is renamed to contextual-lifecycle
  • no-conflicting-life-cycle-hooks is renamed to no-conflicting-lifecycle
  • no-life-cycle-call is renamed to no-lifecycle-call
  • use-life-cycle-interface is renamed to use-lifecycle-interface
  • decorator-not-allowed is renamed to contextual-decorator
  • enforce-component-selector is renamed to use-component-selector
  • no-output-named-after-standard-event is renamed to no-output-native
  • use-host-property-decorator is renamed to no-host-metadata-property
  • use-input-property-decorator is renamed to no-inputs-metadata-property
  • use-output-property-decorator is renamed to no-outputs-metadata-property
  • no-queries-parameter is renamed to no-queries-metadata-property
  • pipe-impure is renamed to no-pipe-impure
  • use-view-encapsulation is renamed to use-component-view-encapsulation
  • i18n is renamed to template-i18n
  • banana-in-box is renamed to template-banana-in-box
  • no-template-call-expression is renamed to template-no-call-expression
  • templates-no-negated-async is renamed to template-no-negated-async
  • trackBy-function is renamed to template-use-track-by-function
  • no-attribute-parameter-decorator is renamed to no-attribute-decorator
  • max-inline-declarations is renamed to component-max-inline-declarations
Bug Fixes
  • rule: template-use-track-by-function not reporting failures involving multiple *ngFor directives (#​721) (9269be6), closes #​718
  • rule: template-no-call-expression should allow $any usages (#​735) (a75c204)
  • rule: no-input-rename reporting some failures incorrectly (#​723) (f692dcb)
  • rule: prefer-inline-decorator should not set a max number of options (#​787) (31b2b6a)
  • rule: add template-accessibility-elements-content to index.ts (#​803) (1e8cbbf), closes #​801
  • rule: NgModule not being handled for contextual-lifecycle and contextual-decorators (#​790) (cedfa2e)
  • rule: prefer-inline-decorator not reporting failures for some cases (#​794) (a76ebbc)
  • update peerDependencies (d5bfbd5)
  • improve ngWalker by preventing an error when a class has no name (#​788) (17c0fe2)
Features

v4.5.0

Compare Source

Bug Fixes
Features

4.4.4 (2018-08-13)

Bug Fixes

4.4.3 (2018-08-06)

Bug Fixes
  • url not passed to transformStyle when using styleUrls (#​686) (5a84041)
  • templates-no-negated-async: not reporting failures for some cases (#​694) (2ffe2ea)

4.4.2 (2018-06-25)

Bug Fixes

4.4.1 (2018-06-23)

Bug Fixes

v4.4.4

Compare Source

Bug Fixes

v4.4.3

Compare Source

Bug Fixes
  • url not passed to transformStyle when using styleUrls (#​686) (5a84041)
  • templates-no-negated-async: not reporting failures for some cases (#​694) (2ffe2ea)

v4.4.2

Compare Source

Bug Fixes

v4.4.1

Compare Source

Bug Fixes

v4.4.0

Compare Source

Bug Fixes
Features

Credits to the codelyzer's maintainers and contributors.

v4.3.0

Compare Source

New Rules

Bug Fixes

  • Possible bug with no-input-rename #​374 f3a53bd.
  • Removed dependency on @angular/platform-browser-dynamic #​525 671e954.
  • Rule contextual-life-cycle too aggressively scoped #​545 dcb4b3e.
  • no-output-named-after-standard-event Does Not Check Output Rename #​537 96d9292.
  • Template Conditional Complexity reports incorrect threshold #​533 5851306.

A lot of credits go to rafaelss95, wKoza. The rest of the amazing people who work on codelyzer, can be found here.

v4.2.1

Compare Source

Bug Fixes

  • Improved peerDependencies range.

v4.2.0

Compare Source

New Rules

  • template-cyclomatic-complexity which limits the estimated Cyclomatic complexity in your templates. Credits to wKoza.
  • template-conditional-complexity which limits the complexity of boolean expressions inside of your templates. Credits to wKoza.

Features

  • Support for Angular version 6 #​524 50fa2d6
  • Cyclomatic complexity rule template-cyclomatic-complexity #​514 3221330
  • Limiting template condition complexity (rule template-conditional-complexity) #​508 bb86295
  • Complete Rules Status section in README and complete Rules Page #​501 1fe9d22

Bug Fixes

  • "extends": ["codelyzer"] is broken #​505 7b76dfa
  • Message for 'use-host-property-decorator' includes invalid link to Angular style docs #​510 5fc77c9

v4.1.0

Compare Source

Features

Bug Fixes

Thanks to @​gbilodeau for NoOutputNamedAfterStandardEventRule and wKoza for the code reviews!

v4.0.2

Compare Source

Bug Fixes
  • Two issues in angular-whitespace related to check-semicolon and check-interpolation #​469 2ef7438
  • Check multiple semicolons inside the directive expressions #​472 e6036d2

Thanks to @​sagittarius-rev for the bug fixes!

v4.0.1

Compare Source

Bug Fixes
  • Fix noOutputOnPrefixRule and rename it to no-output-on-prefix. You can now enable it with:
"no-output-on-prefix": true
  • Fix broken tests for noOutputOnPrefixRule.

v4.0.0

Compare Source

Features

Enable the new rule by adding the following line in your tslint.json config file:

"no-output-on-prefix-name": true

Thanks to @​eromano for the rule implementation!

Breaking Changes
  • The rules templates-use-public, no-access-missing-member, invoke-injectable and template-to-ng-template no longer exist. Remove them from your tslint.json configuration.

v3.2.2

Compare Source

Features
Bug Fixes

v3.2.1

Compare Source

Features
Bug Fixes

v3.2.0

Compare Source

Features
  • i18n best practices #​377 5ef90aa
  • Add a rule which verifies the use of the life cycle methods according to the type of class (Component, Directive, Service,...) #​363 6b042f7
  • Friendlier checking of validator directive names #​397 28ecbdd
Bug Fixes

Thanks to @​wKoza for working on the introduced features, bug fixes and code reviews!

v3.1.2

Compare Source

Features
  • Ensure whitespaces after semicolon in structural dir #​330 25667f9

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.

Bug Fixes
  • Auto fix for check-interpolation part of angularWhitespace is broken #​345 0be8563
  • check-pipe should ignore i18n meaning and description | separator #​359 5aad7f3
  • check-pipe breaks with ngFor #​346 fa08a3b

v3.1.1

Compare Source

Bug Fixes

v3.1.0

Compare Source

New 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]).
  • templates-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
Bug Fixes

v3.0.1

Compare Source

Bug Fixes

v3.0.0

Compare Source

Major release required because of the breaking changes introduced by tslint@5. The ngast support will be pushed to codelyzer@4.

Features
  • Support for tslint@5 #​281 01bffd5 49b1e80
  • Allow more than one selector kind of directives & components #​290 4fa35f6
    "directive-selector": [true, ["attribute", "element"], "sg", "camelCase"],
    "component-selector": [true, ["element", "attribute"], "sg", "kebab-case"],
  • Specs for the support of as syntax in expressions #​289 a7500cb
Refactoring
  • Rename ng2Walker to ngWalker 01bffd5
  • Refactor selector-related rules to depend on less mutable state 4fa35f6

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants