Skip to content

Answer: 50#1453

Open
phhien203 wants to merge 1 commit intotomalaforge:mainfrom
phhien203:phhien203-signal-bug-in-effect
Open

Answer: 50#1453
phhien203 wants to merge 1 commit intotomalaforge:mainfrom
phhien203:phhien203-signal-bug-in-effect

Conversation

@phhien203
Copy link

✅ Challenge Submission Checklist

Start your PR title with: Answer:${challenge_number}

⚠️ Important Notice

If you would like personal feedback or a detailed review, please support the project on GitHub:

You can also submit a PR without sponsorship to:

  • Be listed among the answered challenges, or
  • Receive a review from a community member. 🔥

@github-actions github-actions bot added 50 bug signal effect: effect not triggered answer answer labels Mar 13, 2026
@phhien203
Copy link
Author

The Signal Graph helps visualize the bug in the initial code.
You can see the dependency arrows from the second and third signals to the effect.

CleanShot.2026-03-13.at.16.23.37.mp4

@tomalaforge tomalaforge added the sponsor sponsor the project label Mar 14, 2026
@tomalaforge
Copy link
Owner

very very good explanation. Thank you for that.
I think I will make an article out of your solution and explanation if that's ok.
It shows very well how to understand the angular devtool signal graph and how to solve the issue.
Thanks 🙏

@phhien203
Copy link
Author

Sure. I am looking forward to your article!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

50 bug signal effect: effect not triggered answer answer sponsor sponsor the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants