Last 12 weeks · 0 commits
2 of 6 standards met
First off, very cool example. I'm playing around with this pattern on a help form. The form has its typical onChange events that update the state, etc. But what happens when the form is submitted? How do I get that information up to the parent? Right now I'm having to parse through all the action messages and delegate them to the project updater. This is pretty tedious. It would be cool it there was a way to indicate whether an action is meant to be dispatched to itself, or up to the parent. How does Elm deal with this? I understand this is just a toy example, but its really cool and I think it would be really power if its done right.
Repository: gaearon/react-elmish-example. Description: My personal attempt at understanding Elm architecture Stars: 170, Forks: 10. Primary language: HTML. Languages: HTML (100%). License: MIT. Homepage: http://gaearon.github.io/react-elmish-example Open PRs: 0, open issues: 1. Last activity: 10y ago. Community health: 42%. Top contributors: gaearon.