This is an alternative site for discovering Elm packages. You may be looking for the official Elm package site instead.
A pipeline-friendly library for building JSON decoders.
version 3.0.1
license BSD-3-Clause
native-modules False
elm-version 0.18.0 <= v < 0.19.0
Tag 3.0.1
Committed At 2018-07-24 17:32:39 UTC
elm-lang/core 5.0.0 <= v < 6.0.0 5.1.1

README

elm-decode-pipeline

A library for building decoders using the pipeline (|>) operator and plain function calls.

Motivation

It's common to decode into a record that has a type alias. Here's an example of this from the map3 docs:

type alias Job = { name : String, id : Int, completed : Bool }

point : Decoder Job
point =
  map3 Job
    (field "name" string)
    (field "id" int)
    (field "completed" bool)

This works because a record type alias can be called as a normal function. In that case it accepts one argument for each field (in whatever order the fields are declared in the type alias) and then returns an appropriate record built with those arguments.

The mapN decoders are straightforward, but require manually changing N whenever the field count changes. This library provides functions designed to be used with the |> operator, with the goal of having decoders that are both easy to read and easy to modify.

Examples

Here is a decoder built with this library.

import Json.Decode exposing (int, string, float, nullable, Decoder)
import Json.Decode.Pipeline exposing (decode, required, optional, hardcoded)


type alias User =
  { id : Int
  , email : Maybe String
  , name : String
  , percentExcited : Float
  }


userDecoder : Decoder User
userDecoder =
  decode User
    |> required "id" int
    |> required "email" (nullable string) -- `null` decodes to `Nothing`
    |> optional "name" string "(fallback if name is `null` or not present)"
    |> hardcoded 1.0

In this example:

  • decode is a synonym for succeed (it just reads better here)
  • required "id" int is similar to (field "id" int)
  • optional is like required, but if the field is either null or not present, decoding does not fail; instead it succeeds with the provided fallback value.
  • hardcoded does not look at the provided JSON, and instead always decodes to the same value.

You could use this decoder as follows:

Json.Decode.decodeString
  userDecoder
  """
    {"id": 123, "email": "sam@example.com", "name": "Sam Sample"}
  """

The result would be:

{ id = 123
, email = "sam@example.com"
, name = "Sam Sample"
, percentExcited = 1.0
}

Alternatively, you could use it like so:

Json.Decode.decodeString
  userDecoder
  """
    {"id": 123, "email": "sam@example.com", "percentExcited": "(hardcoded)"}
  """

In this case, the result would be:

{ id = 123
, email = "sam@example.com"
, name = "(fallback if name is `null` or not present)"
, percentExcited = 1.0
}

NoRedInk