2016 at 8:47:01 AM UTC-4, Adam Waselnuk wrote:
>
> This is the last thing blocking me from a migration to 0.17. I can't seem
> to wrap my head around capturing an on "change" event from a select
> element. At this point my app is compiling, but when I toggle the sel
I would suggest the following change:
Embedding Elm in some big JavaScript project is not very hard. It's like
> three lines of JS, but it feels like no one knows about them! So I created
> react-elm-components to make it much more obvious.
change to something like:
Elm is optimized for embed
This is the last thing blocking me from a migration to 0.17. I can't seem
to wrap my head around capturing an on "change" event from a select
element. At this point my app is compiling, but when I toggle the select
dropdown, no messages are sent to the update function. If anyone can point
me to
I asked about this as well and tried an approach where you return a three
element tuple from the update function. The third element is a message for
the parent. This was suggested by Sporto.
I built out a basic working example of that approach
here: https://github.com/AWaselnuk/elm-nested-list
Mark would you be able to provide a link to that solution you are talking
about here?
On Wednesday, May 18, 2016 at 4:40:07 PM UTC-4, Mark Hamburg wrote:
>
> I'm hoping that's not how it is expected to work because it means that a
> view layout decision — we need to put the remove button in with
This is the exact thing I am stuck on right now in my upgrade to 0.17. It
is great to see three approaches outlined here, but would it be possible
for anyone to share some code examples? I am struggling to follow the
conversation a little bit but seeing some code could clear things up.
On Frida
