This package presents a somewhat experimental approach to JSON decoding. Its
API looks very much like the core Json.Decode API. The major differences are
the final decodeString and decodeValue functions, which return a
DecodeResult a.
Decoding with this library can result in one of 4 possible outcomes:
Both the Errors and Warnings types are (mostly) machine readable: they are
implemented as a recursive datastructure that points to the location of the
error in the input json, producing information about what went wrong (i.e. "what
was the expected type, and what did the actual value look like").
Further, this library also adds a few extra Decoders that help with making
assertions about the structure of the JSON while decoding.
For convenience, this library also includes a Json.Decode.Exploration.Pipeline
module which is largely a copy of NoRedInk/elm-decode-pipeline.
All the examples in the documentation are verified by
elm-verify-examples and assume the following imports:
import Json.Encode as Encode
import Json.Decode.Exploration exposing (..)
import Json.Decode.Exploration.Located exposing (Located(..))
import List.Nonempty as Nonempty exposing (Nonempty(Nonempty))
import Array
import DictDecoderRuning a Decoder works largely the same way as it does in the familiar core
library. There is one serious caveat, however:
This library does not allowing decoding non-serializable JS values.
This means that trying to use this library to decode a Value which contains
non-serializable information like functions will not work. It will, however,
result in a BadJson result.
Trying to use this library on cyclic values (like HTML events) is quite likely to blow up completely. Don't try this, except maybe at home.
Run a Decoder on a Value.
Note that this may still fail with a BadJson if there are non-JSON compatible
values in the provided Value. In particular, don't attempt to use this library
when decoding Events - it will blow up. Badly.
Interpret a decode result in a strict way, lifting warnings to errors.
""" ["foo"] """
|> decodeString isArray
|> strict
--> (Here <| Failure "Unused value" (Just <| Encode.string "foo"))
--> |> (AtIndex 0 << Nonempty.fromElement)
--> |> (Err << Nonempty.fromElement)
""" null """
|> decodeString (null "cool")
|> strict
--> Ok "cool"
""" { "foo": "bar" } """
|> decodeString isObject
|> strict
--> (Here <| Failure "Unused value" (Just <| Encode.string "bar"))
--> |> (InField "foo" << Nonempty.fromElement)
--> |> (Err << Nonempty.fromElement)Bad JSON will also result in a Failure, with Nothing as the actual value:
""" foobar """
|> decodeString string
|> strict
--> (Here <| Failure "Invalid JSON" Nothing)
--> |> (Err << Nonempty.fromElement)Errors will still be errors, of course.
""" null """
|> decodeString string
|> strict
--> (Here <| Expected TString Encode.null)
--> |> (Err << Nonempty.fromElement)Decoding can have 4 different outcomes:
BadJson occurs when the JSON string isn't valid JSON, or the Value
contains non-JSON primitives like functions.Errors means errors occurred while running your decoder and contains the
Errors that occurred.WithWarnings means decoding succeeded but produced one or more
Warnings.Success is the best possible outcome: All went well!A simple type alias for Json.Decode.Value.
Decoding may fail with 1 or more errors, so Errors is a
Nonempty of errors.
The most basic kind of an Error is Failure, which comes annotated with
a string describing the failure, and the JSON Value that was encountered
instead.
The other cases describe the "path" to where the error occurred.
Stringifies errors to a human readable string.
Decoding may generate warnings. In case the result is a WithWarnings, you
will have 1 or more warnings, as a Nonempty list.
Like with errors, the most basic warning is an unused value. The other cases describe the path to the warnings.
Stringifies warnings to a human readable string.
An enumeration of the different types that could be expected by a decoder.
Kind of the core idea of this library. Think of it as a piece of data that
describes how to read and transform JSON. You can use decodeString and
decodeValue to actually execute a decoder on JSON.
Decode a string.
""" "hello world" """
|> decodeString string
--> Success "hello world"
""" 123 """
|> decodeString string
--> Errors (Nonempty (Here <| Expected TString (Encode.int 123)) [])Decode a boolean value.
""" [ true, false ] """
|> decodeString (list bool)
--> Success [ True, False ]Decode a number into an Int.
""" 123 """
|> decodeString int
--> Success 123
""" 0.1 """
|> decodeString int
--> Errors <|
--> Nonempty
--> (Here <| Expected TInt (Encode.float 0.1))
--> []Decode a number into a Float.
""" 12.34 """
|> decodeString float
--> Success 12.34
""" 12 """
|> decodeString float
--> Success 12
""" null """
|> decodeString float
--> Errors (Nonempty (Here <| Expected TNumber Encode.null) [])Decodes successfully and wraps with a Just. If the values is null
succeeds with Nothing.
""" [ { "foo": "bar" }, { "foo": null } ] """
|> decodeString (list <| field "foo" <| nullable string)
--> Success [ Just "bar", Nothing ]Decode a list of values, decoding each entry with the provided decoder.
""" [ "foo", "bar" ] """
|> decodeString (list string)
--> Success [ "foo", "bar" ]
""" [ "foo", null ] """
|> decodeString (list string)
--> Errors <|
--> Nonempty
--> (AtIndex 1 <|
--> Nonempty (Here <| Expected TString Encode.null) []
--> )
--> []Convenience function. Decode a JSON array into an Elm Array.
""" [ 1, 2, 3 ] """
|> decodeString (array int)
--> Success <| Array.fromList [ 1, 2, 3 ]Convenience function. Decode a JSON object into an Elm Dict String.
""" { "foo": "bar", "bar": "hi there" } """
|> decodeString (dict string)
--> Success <| Dict.fromList
--> [ ( "bar", "hi there" )
--> , ( "foo", "bar" )
--> ]Decode a JSON object into a list of key-value pairs. The decoder you provide will be used to decode the values.
""" { "foo": "bar", "hello": "world" } """
|> decodeString (keyValuePairs string)
--> Success [ ( "foo", "bar" ), ( "hello", "world" ) ]A Decoder to ascertain that a JSON value is in fact, a JSON object.
Using this decoder marks the object itself as used, without touching any of its children. It is, as such, fairly well behaved.
""" { } """
|> decodeString isObject
--> Success ()
""" [] """
|> decodeString isObject
--> Errors <| Nonempty.fromElement <| Here <| Expected TObject (Encode.list [])Similar to isObject, a decoder to ascertain that a JSON value is a JSON
array.
""" [] """
|> decodeString isArray
--> Success ()
""" [ "foo" ] """
|> decodeString isArray
--> WithWarnings (Nonempty (AtIndex 0 (Nonempty (Here <| UnusedValue <|
Encode.string "foo") [])) []) ()
""" null """
|> decodeString isArray
--> Errors <| Nonempty.fromElement <| Here <| Expected TArray Encode.nullDecode the content of a field using a provided decoder.
""" { "foo": "bar" } """
|> decodeString (field "foo" string)
--> Success "bar"
""" [ { "foo": "bar" }, { "foo": "baz", "hello": "world" } ] """
|> decodeString (list (field "foo" string))
--> WithWarnings expectedWarnings [ "bar", "baz" ]
expectedWarnings : Warnings
expectedWarnings =
UnusedValue (Encode.string "world")
|> Here
|> Nonempty.fromElement
|> InField "hello"
|> Nonempty.fromElement
|> AtIndex 1
|> Nonempty.fromElementDecodes a value at a certain path, using a provided decoder. Essentially,
writing at [ "a", "b", "c" ] string is sugar over writing
field "a" (field "b" (field "c" string))}.
""" { "a": { "b": { "c": "hi there" } } } """
|> decodeString (at [ "a", "b", "c" ] string)
--> Success "hi there"Decode a specific index using a specified Decoder.
""" [ "hello", 123 ] """
|> decodeString (map2 (,) (index 0 string) (index 1 int))
--> Success ( "hello", 123 )
""" [ "hello", "there" ] """
|> decodeString (index 1 string)
--> WithWarnings
--> (Nonempty (AtIndex 0 <| Nonempty (Here <| UnusedValue (Encode.string "hello")) []) [])
--> "there"Decodes successfully and wraps with a Just, handling failure by succeeding
with Nothing.
""" [ "foo", 12 ] """
|> decodeString (list <| maybe string)
--> WithWarnings expectedWarnings [ Just "foo", Nothing ]
expectedWarnings : Warnings
expectedWarnings =
UnusedValue (Encode.int 12)
|> Here
|> Nonempty.fromElement
|> AtIndex 1
|> Nonempty.fromElementTries a bunch of decoders. The first one to not fail will be the one used.
If all fail, the errors are collected into a BadOneOf.
""" [ 12, "whatever" ] """
|> decodeString (list <| oneOf [ map toString int, string ])
--> Success [ "12", "whatever" ]
""" null """
|> decodeString (oneOf [ string, map toString int ])
--> Errors <| Nonempty.fromElement <| Here <| BadOneOf
--> [ Nonempty.fromElement <| Here <| Expected TString Encode.null
--> , Nonempty.fromElement <| Here <| Expected TInt Encode.null
--> ]Required when using (mutually) recursive decoders.
Extract a piece without actually decoding it.
If a structure is decoded as a value, everything in the structure will be
considered as having been used and will not appear in UnusedValue warnings.
""" [ 123, "world" ] """
|> decodeString value
--> Success (Encode.list [ Encode.int 123, Encode.string "world" ])Decode a null and succeed with some value.
""" null """
|> decodeString (null "it was null")
--> Success "it was null"Note that undefined and null are not the same thing. This cannot be used to
verify that a field is missing, only that it is explicitly set to null.
""" { "foo": null } """
|> decodeString (field "foo" (null ()))
--> Success ()
""" { } """
|> decodeString (field "foo" (null ()))
--> Errors <|
--> Nonempty
--> (Here <| Expected (TObjectField "foo") (Encode.object []))
--> []Useful for checking a value in the JSON matches the value you expect it to have. If it does, succeeds with the second decoder. If it doesn't it fails.
This can be used to decode union types:
type Pet = Cat | Dog | Rabbit
petDecoder : Decoder Pet
petDecoder =
oneOf
[ check string "cat" <| succeed Cat
, check string "dog" <| succeed Dog
, check string "rabbit" <| succeed Rabbit
]
""" [ "dog", "rabbit", "cat" ] """
|> decodeString (list petDecoder)
--> Success [ Dog, Rabbit, Cat ]A decoder that will ignore the actual JSON and succeed with the provided value. Note that this may still fail when dealing with an invalid JSON string.
If a value in the JSON ends up being ignored because of this, this will cause a warning.
""" null """
|> decodeString (value |> andThen (\_ -> succeed "hello world"))
--> Success "hello world"
""" null """
|> decodeString (succeed "hello world")
--> WithWarnings
--> (Nonempty (Here <| UnusedValue Encode.null) [])
--> "hello world"
""" foo """
|> decodeString (succeed "hello world")
--> BadJsonIgnore the json and fail with a provided message.
""" "hello" """
|> decodeString (fail "failure")
--> Errors (Nonempty (Here <| Failure "failure" (Just <| Encode.string "hello")) [])Add a warning to the result of a decoder.
For example, imagine we are upgrading some internal JSON format. We might add a temporary workaround for backwards compatibility. By adding a warning to the decoder, we can flag these or print them during development.
decoder : Decoder (List Int)
decoder =
oneOf
[ list int
, int |> map List.singleton |> warn "Converted to list"
]
expectedWarnings : Warnings
expectedWarnings =
Warning "Converted to list" (Encode.int 123)
|> Here
|> Nonempty.fromElement
""" 123 """
|> decodeString decoder
--> WithWarnings expectedWarnings [ 123 ]Note that warnings added to a failing decoder won't show up.
""" null """
|> decodeString (warn "this might be null" int)
--> Errors (Nonempty.fromElement (Here <| Expected TInt Encode.null))Chain decoders where one decoder depends on the value of another decoder.
Note: If you run out of map functions, take a look at the pipeline module which makes it easier to handle large objects.
Useful for transforming decoders.
""" "foo" """
|> decodeString (map String.toUpper string)
--> Success "FOO"Combine 2 decoders.
Combine 3 decoders.
Combine 4 decoders.
Combine 5 decoders.
Combine 6 decoders.
Combine 7 decoders.
Combine 8 decoders.
Decode an argument and provide it to a function in a decoder.
decoder : Decoder String
decoder =
succeed (String.repeat)
|> andMap (field "count" int)
|> andMap (field "val" string)
""" { "val": "hi", "count": 3 } """
|> decodeString decoder
--> Success "hihihi"Last but not least, an extra import to allow elm-verify-examples to actually verify all the examples:
import DocVerificationHelpers exposing (Pet(..))
Decode a JSON string. If the string isn't valid JSON, this will fail with a
BadJsonresult.