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

refactor: replace effects with linkedSignals #32

Merged
merged 1 commit into from
Dec 10, 2024
Merged

Conversation

tutkli
Copy link
Owner

@tutkli tutkli commented Dec 10, 2024

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Effects are used to update signal values.

Closes #

What is the new behavior?

New linkedSignal is used where it makes sense.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@tutkli tutkli merged commit 51b0a17 into angular-19 Dec 10, 2024
2 checks passed
@tutkli tutkli deleted the linkedSignals branch December 10, 2024 10:33
tutkli pushed a commit that referenced this pull request Dec 10, 2024
## [3.0.0](v2.0.2...v3.0.0) (2024-12-10)

### ⚠ BREAKING CHANGES

* minimal angular version is now v19

### Features

* update to angular v19 ([bf70b01](bf70b01))

### Bug Fixes

* toast remaining time is handled after render ([b19de68](b19de68))

### Chores

* update package-lock.json ([7af1c9a](7af1c9a))

### Refactoring

* replace effects with linkedSignals ([#32](#32)) ([51b0a17](51b0a17))
@tutkli
Copy link
Owner Author

tutkli commented Dec 10, 2024

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

1 participant