Timeline for Patterns to allow for versatile data-flow hooks in Javascript
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2016 at 16:36 | comment | added | Sunyatasattva | Thanks for the answer, it was a nice read; however, this deals mostly with the first part of my question: event-systems as hooks. The thing with events is that the code that triggers them rightly doesn't care of who is subscribed; as such, events don't return values that can be passed around and manipulated. In my case, I need a way for other parts of the components to "filter" around specific data exposed by a specific component. As far as I know, this is specifically not allowed inRedux for good reasons. That's why I was also asking for an alternative, since this may be an anti-pattern. | |
| Aug 5, 2016 at 7:12 | review | First posts | |||
| Sep 4, 2016 at 7:12 | |||||
| Aug 5, 2016 at 7:10 | history | answered | Lunster | CC BY-SA 3.0 |