Hacker News new | past | comments | ask | show | jobs | submit login

Have you used it? That’s like saying the Chrome debugger or CPU call stacks are overrated. It’s a debug feature that any React+Redux app can use to trace back why something happened. I’ve used it a few times, and when you need it because you don’t understand why an action was triggered, it’s super convenient.



You know what happened, not how. Was it a user click on this button or another button? Or was the action triggered by a saga?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: