28: Ports Multiplying

We are back to meow notes, adding our onClick event from Elm back to React to route either to a new note, or an existing note by note.id. This is going to require us to poke another hole in our ports, but remember Murphy's warning, not to treat this like http methods, so lets keep that in mind as we move forward.

Read

27: State of Elm

I thought it would be great to talk about the current state of Elm, with the yearly survey closing in a few days, talk about what previous year’s results have told us, go over what the questions for this year and how I answered them, and make any predictions for the out come.

Read

26: Ports, JSON, And Elm render

The last 10%. We left off our app with being able to pass the return JSON from our fetch promise to get a list of notes through ports to Elm, and debug logging that out. At this point I thought, "success!". You might even recall, I glossed over rendering it to a list, totally spaced the click event needed to make the list actually do something. So today we take the work of getting the data to work, to the work needed to get it back to working functionality using Elm.

Read

25: Now With More Elm

Now we have Elm working inside of our react app, its time to pick a spot, feature, or pain point and get to refactoring with Elm. There are several ways to tackle this, we'll cover a few of the different ones, and what ultimately worked for us in meow notes.

Read

24: Adding Elm

We've got our project up and running, and now's the time to start refactoring it into Elm. How do we get Elm to play nice with our React app, better still what part of the app should we start with? There seems to be more questions than answers, but we'll work our way through it.

Read
Powered by Contentful