refactor(body-cell): migrate to signals #347
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chintankavathia
force-pushed
the
refactor/body/cell/signals
branch
3 times, most recently
from
2b88867 to
da62150
Compare
spike-rabbit
requested changes
Oct 1, 2025
projects/ngx-datatable/src/lib/components/body/body-cell.component.ts
Outdated
Show resolved
Hide resolved
chintankavathia
force-pushed
the
refactor/body/cell/signals
branch
from
da62150 to
99a4cbe
Compare
9 tasks
chintankavathia
force-pushed
the
refactor/body/cell/signals
branch
from
99a4cbe to
973baa6
Compare
spike-rabbit
force-pushed
the
refactor/body/cell/signals
branch
from
973baa6 to
be9fbc5
Compare
|
🎉 This PR is included in version 24.3.1 🎉 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
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: