bitterjug

Http in Elm

The Elm Architecture Recap

1. Elm looks after your system state, or model.
2. Set it up with init
3. All input is via messages (Msg): data values you define
4. All side-effects are via commands (Cmd) data values defined by Elm
5. The only 'callbacks' are update and view
6. On input (from, e.g., user or servers) Elm calls update passing a Msg, and the current model

bitterjug

Keybase proof

I hereby claim:

• I am bitterjug on github.
• I am bitterjug (https://keybase.io/bitterjug) on keybase.
• I have a public key ASD0Pg6TeIdISMoZL2PTwTKwe7MKRVj8kMASCTbkKWKexgo

To claim this, I am signing this object:

bitterjug

#!/usr/bin/env bash
# Add the branch name as the first line of the commit message.
# .git/hooks/prepare-commit-msg

NAME=$(git rev-parse --abbrev-ref HEAD)
[[ $(head -1 $1) =~ ^${NAME} ]] || echo -e "$NAME $(cat $1)" > "$1"

bitterjug

Elm Europe 2017

Elm Europe June 2017

Twenty odd speakers, including keynotes from Evan and Richard who both spoke about how Elm programs grow and evolve. Richard's talk and Evan's Talk are on the YouTube Channel.

Matthew Giffith's presentation and source code on

bitterjug

Cambridge Elm Meetup: Write some Elm

Here's the plan:

Write a spell-checker app using the Montana Flynn Spellcheck API hosted on Mashape.com. (You need a Mashape API key to use this API. I signed up with my github account.) Your app may be arbitrarily complex, but a simple one might comprise: a text area to enter text, a "check spelling" button and a place to show the suggestion from the api.

If you don't have Elm installed, use the awesome Ellie editor online.

Depending on your familiarity with Elm, you might like some guidance. This is what I did: