yaml-0.8.2.4: Support for parsing and rendering YAML documents.

Safe HaskellNone

Data.Yaml

Description

Provides a high-level interface for processing YAML files.

This module reuses most of the infrastructure from the aeson package. This means that you can use all of the existing tools for JSON processing for processing YAML files. As a result, much of the documentation below mentions JSON; do not let that confuse you, it's intentional.

For the most part, YAML content translates directly into JSON, and therefore there is very little data loss. If you need to deal with YAML more directly (e.g., directly deal with aliases), you should use the Text.Libyaml module instead.

For documentation on the aeson types, functions, classes, and operators, please see the Data.Aeson module of the aeson package.

Types

data Value

A JSON value represented as a Haskell value.

Constructors

Instances

data Parser a

A continuation-based parser type.

Instances

type Object = HashMap Text Value

A JSON "object" (key/value map).

type Array = Vector Value

A JSON "array" (sequence).

data ParseException Source

Constructors

Instances

Constructors and accessors

object :: [Pair] -> Value

Create a Value from a list of name/value Pair s. If duplicate keys arise, earlier keys and their associated values win.

array :: [Value] -> Value Source

(.=) :: ToJSON a => Text -> a -> Pair

Construct a Pair from a key and a value.

(.:) :: FromJSON a => Object -> Text -> Parser a

Retrieve the value associated with the given key of an Object . The result is empty if the key is not present or the value cannot be converted to the desired type.

This accessor is appropriate if the key and value must be present in an object for it to be valid. If the key and value are optional, use '(.:?)' instead.

(.:?) :: FromJSON a => Object -> Text -> Parser (Maybe a)

Retrieve the value associated with the given key of an Object . The result is Nothing if the key is not present, or empty if the value cannot be converted to the desired type.

This accessor is most useful if the key and value can be absent from an object without affecting its validity. If the key and value are mandatory, use '(.:)' instead.

(.!=) :: Parser (Maybe a) -> a -> Parser a

Helper for use in combination with .:? to provide default values for optional JSON object fields.

This combinator is most useful if the key and value can be absent from an object without affecting its validity and we know a default value to assign in that case. If the key and value are mandatory, use '(.:)' instead.

Example usage:

 v1 <- o .:?  "opt_field_with_dfl" .!= "default_val"
 v2 <- o .:  "mandatory_field"
 v3 <- o .:?  "opt_field2"

Parsing

parseMonad :: Monad m => (a -> Parser b) -> a -> m bSource

parseEither :: (a -> Parser b) -> a -> Either String b

Run a Parser with an Either result type.

parseMaybe :: (a -> Parser b) -> a -> Maybe b

Run a Parser with a Maybe result type.

Classes

class ToJSON a where

A type that can be converted to JSON.

An example type and instance:

{-# LANGUAGE OverloadedStrings #-}
data Coord { x :: Double, y :: Double }
instance ToJSON Coord where
 toJSON (Coord x y) = object  ["x" .=  x, "y" .=  y]

Note the use of the OverloadedStrings language extension which enables Text values to be written as string literals.

Instead of manually writing your ToJSON instance, there are three options to do it automatically:

  • Data.Aeson.TH provides template-haskell functions which will derive an instance at compile-time. The generated instance is optimized for your type so will probably be more efficient than the following two options:
  • Data.Aeson.Generic provides a generic toJSON function that accepts any type which is an instance of Data.
  • If your compiler has support for the DeriveGeneric and DefaultSignatures language extensions (GHC 7.2 and newer), toJSON will have a default generic implementation.

To use the latter option, simply add a deriving Generic clause to your datatype and declare a ToJSON instance for your datatype without giving a definition for toJSON.

For example the previous example can be simplified to just:

{-# LANGUAGE DeriveGeneric #-}
import GHC.Generics
data Coord { x :: Double, y :: Double } deriving Generic
instance ToJSON Coord

Methods

toJSON :: a -> Value

Instances

class FromJSON a where

A type that can be converted from JSON, with the possibility of failure.

When writing an instance, use empty , mzero, or fail to make a conversion fail, e.g. if an Object is missing a required key, or the value is of the wrong type.

An example type and instance:

{-# LANGUAGE OverloadedStrings #-}
data Coord { x :: Double, y :: Double }
instance FromJSON Coord where
 parseJSON (Object  v) = Coord <$> 
 v .:  "x" <*> 
 v .:  "y"
-- A non-Object  value is of the wrong type, so use mzero to fail.
 parseJSON _ = mzero

Note the use of the OverloadedStrings language extension which enables Text values to be written as string literals.

Instead of manually writing your FromJSON instance, there are three options to do it automatically:

  • Data.Aeson.TH provides template-haskell functions which will derive an instance at compile-time. The generated instance is optimized for your type so will probably be more efficient than the following two options:
  • Data.Aeson.Generic provides a generic fromJSON function that parses to any type which is an instance of Data.
  • If your compiler has support for the DeriveGeneric and DefaultSignatures language extensions, parseJSON will have a default generic implementation.

To use this, simply add a deriving Generic clause to your datatype and declare a FromJSON instance for your datatype without giving a definition for parseJSON.

For example the previous example can be simplified to just:

{-# LANGUAGE DeriveGeneric #-}
import GHC.Generics
data Coord { x :: Double, y :: Double } deriving Generic
instance FromJSON Coord

Methods

parseJSON :: Value -> Parser a

Instances

FromJSON a => FromJSON [a]
(Ord a, FromJSON a) => FromJSON (Set a)
(Eq a, Hashable a, FromJSON a) => FromJSON (HashSet a)
(Prim a, FromJSON a) => FromJSON (Vector a)
(FromJSON a, FromJSON b) => FromJSON (Either a b)
(FromJSON a, FromJSON b) => FromJSON (a, b)
(FromJSON a, FromJSON b, FromJSON c) => FromJSON (a, b, c)
(FromJSON a, FromJSON b, FromJSON c, FromJSON d) => FromJSON (a, b, c, d)

Encoding/decoding

encode :: ToJSON a => a -> ByteString Source

encodeFile :: ToJSON a => FilePath -> a -> IO ()Source

decode :: FromJSON a => ByteString -> Maybe aSource

decodeFile :: FromJSON a => FilePath -> IO (Maybe a)Source

Better error information

decodeEither :: FromJSON a => ByteString -> Either String aSource

More control over decoding

decodeHelper :: FromJSON a => Source Parse Event -> IO (Either ParseException (Either String a))Source

AltStyle によって変換されたページ (->オリジナル) /