From 3745e7605e045c5e14d6c789acad04a1fd4f99b1 Mon Sep 17 00:00:00 2001 From: Hitesh Jasani Date: Tue, 11 Aug 2015 23:32:31 -0400 Subject: [PATCH] Fix incorrect field reference to avoid confusion. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 19fc131..97d2d3a 100644 --- a/README.md +++ b/README.md @@ -520,7 +520,7 @@ In the case of `RequestMore` first return the existing model. The user just clic NewGif (Just "http://s3.amazonaws.com/giphygifs/media/ka1aeBvFCSLD2/giphy.gif") ``` -It returns a `Maybe` because the request to the server may fail. That `Action` will get fed right back into our `update` function. So when we take the `NewGif` route we just update the current `image` if possible. If the request failed, we just stick with the current `model.image`. +It returns a `Maybe` because the request to the server may fail. That `Action` will get fed right back into our `update` function. So when we take the `NewGif` route we just update the current `gifUrl` if possible. If the request failed, we just stick with the current `model.gifUrl`. We see the same kind of thing happening in `init` which defines the initial model and asks for a GIF in the correct topic from giphy.com’s API.