canceraiddev / elm-pages / OptimizedDecoder.Pipeline

Json.Decode.Pipeline

Use the (|>) operator to build JSON decoders.

Decoding fields

required : String -> OptimizedDecoder.Decoder a -> OptimizedDecoder.Decoder (a -> b) -> OptimizedDecoder.Decoder b

Decode a required field.

import Json.Decode.Exploration exposing (..)

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

userDecoder : Decoder User
userDecoder =
    decode User
        |> required "id" int
        |> required "name" string
        |> required "email" string

""" {"id": 123, "email": "sam@example.com", "name": "Sam"} """
    |> decodeString userDecoder
--> Success { id = 123, name = "Sam", email = "sam@example.com" }

requiredAt : List String -> OptimizedDecoder.Decoder a -> OptimizedDecoder.Decoder (a -> b) -> OptimizedDecoder.Decoder b

Decode a required nested field.

import Json.Decode.Exploration exposing (..)

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

userDecoder : Decoder User
userDecoder =
    decode User
        |> required "id" int
        |> requiredAt [ "profile", "name" ] string
        |> required "email" string

"""
{
    "id": 123,
    "email": "sam@example.com",
    "profile": { "name": "Sam" }
}
"""
    |> decodeString userDecoder
--> Success { id = 123, name = "Sam", email = "sam@example.com" }

optional : String -> OptimizedDecoder.Decoder a -> a -> OptimizedDecoder.Decoder (a -> b) -> OptimizedDecoder.Decoder b

Decode a field that may be missing or have a null value. If the field is missing, then it decodes as the fallback value. If the field is present, then valDecoder is used to decode its value. If valDecoder fails on a null value, then the fallback is used as if the field were missing entirely.

import Json.Decode.Exploration exposing (..)

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

userDecoder : Decoder User
userDecoder =
    decode User
        |> required "id" int
        |> optional "name" string "blah"
        |> required "email" string

""" { "id": 123, "email": "sam@example.com" } """
    |> decodeString userDecoder
--> Success { id = 123, name = "blah", email = "sam@example.com" }

Because valDecoder is given an opportunity to decode null values before resorting to the fallback, you can distinguish between missing and null values if you need to:

userDecoder2 =
    decode User
        |> required "id" int
        |> optional "name" (oneOf [ string, null "NULL" ]) "MISSING"
        |> required "email" string

Note also that this behaves slightly different than the stock pipeline package.

In the stock pipeline package, running the following decoder with an array as the input would succeed.

fooDecoder =
    decode identity
        |> optional "foo" (maybe string) Nothing

In this package, such a decoder will error out instead, saying that it expected the input to be an object. The key "foo" is optional, but it really does have to be an object before we even consider trying your decoder or returning the fallback.

optionalAt : List String -> OptimizedDecoder.Decoder a -> a -> OptimizedDecoder.Decoder (a -> b) -> OptimizedDecoder.Decoder b

Decode an optional nested field.

hardcoded : a -> OptimizedDecoder.Decoder (a -> b) -> OptimizedDecoder.Decoder b

Rather than decoding anything, use a fixed value for the next step in the pipeline. harcoded does not look at the JSON at all.

import Json.Decode.Exploration exposing (..)


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

userDecoder : Decoder User
userDecoder =
    decode User
        |> required "id" int
        |> hardcoded "Alex"
        |> required "email" string

""" { "id": 123, "email": "sam@example.com" } """
    |> decodeString userDecoder
--> Success { id = 123, name = "Alex", email = "sam@example.com" }

custom : OptimizedDecoder.Decoder a -> OptimizedDecoder.Decoder (a -> b) -> OptimizedDecoder.Decoder b

Run the given decoder and feed its result into the pipeline at this point.

Consider this example.

import Json.Decode.Exploration exposing (..)


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

userDecoder : Decoder User
userDecoder =
    decode User
        |> required "id" int
        |> custom (at [ "profile", "name" ] string)
        |> required "email" string

"""
{
    "id": 123,
    "email": "sam@example.com",
    "profile": {"name": "Sam"}
}
"""
    |> decodeString userDecoder
--> Success { id = 123, name = "Sam", email = "sam@example.com" }

Beginning and ending pipelines

decode : a -> OptimizedDecoder.Decoder a

Begin a decoding pipeline. This is a synonym for Json.Decode.succeed, intended to make things read more clearly.

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

userDecoder : Decoder User
userDecoder =
    decode User
        |> required "id" int
        |> required "email" string
        |> optional "name" string ""

resolve : OptimizedDecoder.Decoder (OptimizedDecoder.Decoder a) -> OptimizedDecoder.Decoder a

Convert a Decoder (Result x a) into a Decoder a. Useful when you want to perform some custom processing just before completing the decoding operation.

import Json.Decode.Exploration exposing (..)

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

userDecoder : Decoder User
userDecoder =
    let
        -- toDecoder gets run *after* all the
        -- (|> required ...) steps are done.
        toDecoder : Int -> String -> String -> Int -> Decoder User
        toDecoder id name email version =
            if version >= 2 then
                succeed (User id name email)
            else
                fail "This JSON is from a deprecated source. Please upgrade!"
    in
    decode toDecoder
        |> required "id" int
        |> required "name" string
        |> required "email" string
        |> required "version" int
        -- version is part of toDecoder,
        -- but it is not a part of User
        |> resolve

"""
{
    "id": 123,
    "name": "Sam",
    "email": "sam@example.com",
    "version": 3
}
"""
    |> decodeString userDecoder
--> Success { id = 123, name = "Sam", email = "sam@example.com" }

Verified docs

The examples all expect imports set up like this:

import Json.Decode.Exploration exposing (..)
import Json.Decode.Exploration.Pipeline exposing (..)
import Json.Decode.Exploration.Located exposing (Located(..))
import Json.Encode as Encode
import List.Nonempty as Nonempty

For automated verification of these examples, this import is also required. Please ignore it.

import DocVerificationHelpers exposing (User)