36: Elm Second Component

We find that looking closer at replacing new note creation isn't as easy and 1, 2, 3! Who would have that. You'd think after the 10,000th time we'd learn, it's never as straight forward as we thought. Ok, so let's regroup, come up with a strategy for getting this done and go from there.

Read

35: Elm Forms

We've made a lot of progress over the past weeks and months. It's time to sink our teeth into New Notes form. At it's basic we want to have the text into, attach a file, and a create button. And then more!!!

Read

34: Elm With Flags

So we are at that point when it's time to expand our app to have more than a single component in Elm. A couple weeks ago we started down the path of routing, by refactoring the core of our app, main state and routing, into Elm. This turned out to be a bit more daunting the more we looked into it. So let's try something else...

Read

33: Stay in production

So I all the rewriting and refactoring, we haven't shipped out a release of meow notes in a while. The first rule of our refactor was to always keep it in a state of usability. That way problems we have, or choices we make will come up sooner, rather than later!

Read

32: Elm Routing, the basics

As I'm looking at the ways that I can get tackle having Elm over take our React app, I'm a bit stumped by routing. For review, we've got an onClick event in our list of notes in the 'Home' module that should take use from the root of our application '/', to notes with at unique noteId in the url like '/notes/:noteId' this let's us grab that id from the route and fetch the details of that particular note. We're not leveraging react router dom, which is what I've relied on for a long time now. So, how does this work ?

Read
Powered by Contentful