antoantonyk / password-strength-meter

To display the strength of the password with a visual feedback. PasswordStrengthMeter use zxcvbn to estimate the strength of the password and also provide a visual feedback with suggestions and warning messages.
https://antoantonyk.github.io/password-strength-meter/
MIT License
63 stars 33 forks source link

chore(deps): bump @angular/router from 17.0.0 to 17.3.1 #848

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps @angular/router from 17.0.0 to 17.3.1.

Release notes

Sourced from @​angular/router's releases.

v17.3.1

17.3.1 (2024-03-20)

compiler

Commit Description
fix - c0788200e2 capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Description
fix - 99e9474aa2 symbol feature detection for the compiler (#54711)

v17.3.0

17.3.0 (2024-03-13)

compiler

Commit Description
feat - 1a6beae8a2 Enable template pipeline by default. (#54571)
fix - f386a04c9d handle two-way bindings to signal-based template variables in instruction generation (#54714)
fix - 1f129f114e not catching for loop empty tracking expressions (#54772)

compiler-cli

Commit Description
fix - 12dc4d074e account for as expression in docs extraction (#54414)
fix - da7fbb40f0 detect when the linker is working in unpublished angular and widen supported versions (#54439)
fix - 492e03f699 flag two-way bindings to non-signal values in templates (#54714)
fix - 5afa4f0ec1 support ModuleWithProviders literal detection with typeof (#54650)

core

Commit Description
feat - 331b16efd2 add API to inject attributes on the host node (#54604)
feat - fb540e169a add migration for invalid two-way bindings (#54630)
feat - c687b8f453 expose new output() API (#54650)
feat - c809069f21 introduce outputFromObservable() interop function (#54650)
feat - aff65fd1f4 introduce outputToObservable interop helper (#54650)
feat - 974958913c support TypeScript 5.4 (#54414)
fix - 39a50f9a8d ensure all initializer functions run in an injection context (#54761)
fix - 243ccce624 exclude class attribute intended for projection matching from directive matching (#54800)
fix - 2909e9817d prevent infinite loops in clobbered elements check (#54425)
fix - 7243c704cf return a readonly signal on asReadonly. (#54706)
perf - bb35414a38 speed up retrieval of DestroyRef in EventEmitter (#54748)

http

Commit Description
fix - 8d37ed035c exclude caching for authenticated HTTP requests (#54746)

router

Commit Description
feat - c1c7384e02 Add reusable types for router guards (#54580)

... (truncated)

Changelog

Sourced from @​angular/router's changelog.

17.3.1 (2024-03-20)

compiler

Commit Type Description
c0788200e2 fix capture data bindings for content projection purposes in blocks (#54876)

compiler-cli

Commit Type Description
99e9474aa2 fix symbol feature detection for the compiler (#54711)

18.0.0-next.0 (2024-03-14)

Breaking Changes

core

  • OnPush views at the root of the application need to be marked dirty for their host bindings to refresh. Previously, the host bindings were refreshed for all root views without respecting the OnPush change detection strategy.
  • The ComponentFixture autoDetect feature will no longer refresh the component's host view when the component is OnPush and not marked dirty. This exposes existing issues in components which claim to be OnPush but do not correctly call markForCheck when they need to be refreshed. If this change causes test failures, the easiest fix is to change the component to ChangeDetectionStrategy.Default.
  • When Angular runs change detection, it will continue to refresh any views attached to ApplicationRef that are still marked for check after one round completes. In rare cases, this can result in infinite loops when certain patterns continue to mark views for check using ChangeDetectorRef.detectChanges. This will be surfaced as a runtime error with the NG0103 code.
  • The ComponentFixture.autoDetect feature now executes change detection for the fixture within ApplicationRef.tick. This more closely matches the behavior of how a component would refresh in production. The order of component refresh in tests may be slightly affected as a result, especially when dealing with additional components attached to the application, such as dialogs. Tests sensitive to this type of change (such as screenshot tests) may need to be updated. Concretely, this change means that the component will refresh before additional views attached to ApplicationRef (i.e. dialog components). Prior to this change, the fixture component would refresh after other views attached to the application.
  • The exact timing of change detection execution when using event or run coalescing with NgZone is now the first of either setTimeout or requestAnimationFrame. Code which relies on this timing (usually by accident) will need to be adjusted. If a callback needs to execute after change detection, we recommend afterNextRender instead of something like setTimeout.
  • Newly created and views marked for check and reattached

... (truncated)

Commits
  • 7225485 fix(router): Navigations triggered by cancellation events should cancel previ...
  • c1c7384 feat(router): Add reusable types for router guards (#54580)
  • d3b273a fix(router): Clear internal transition when navigation finalizes (#54261)
  • a9741e6 docs(router): deprecate RouterTestingModule (#54466)
  • b857aaf refactor: migrate router to prettier formatting (#54318)
  • 0dfbde9 Revert "fix(router): Clear internal transition when navigation finalizes (#54...
  • 6681292 fix(router): Clear internal transition when navigation finalizes (#54261)
  • 4f7edaa refactor(router): RouterLink read urlTree only once (#53817)
  • d6e4931 refactor(router): remove duplicate helper methods (#53762)
  • 15c4811 refactor(router): Update integration tests to cover navigation and history AP...
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @antoantonyk.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 7 months ago

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

dependabot[bot] commented 7 months ago

Superseded by #856.