Hoogle Search

Within LTS Haskell 24.38 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. module Text.XML.Stream.Parse

    This module provides both a native Haskell solution for parsing XML documents into a stream of events, and a set of parser combinators for dealing with a stream of events. As a simple example: 

    >>> :set -XOverloadedStrings

>>> import Conduit (runConduit, (.|))

>>> import Data.Text (Text, unpack)

>>> import Data.XML.Types (Event)

>>> data Person = Person Int Text Text deriving Show

>>> :{
let parsePerson :: MonadThrow m => ConduitT Event o m (Maybe Person)
parsePerson = tag' "person" parseAttributes $ \(age, goodAtHaskell) -> do
name <- content
return $ Person (read $ unpack age) name goodAtHaskell
where parseAttributes = (,) <$> requireAttr "age" <*> requireAttr "goodAtHaskell" <* ignoreAttrs
parsePeople :: MonadThrow m => ConduitT Event o m (Maybe [Person])
parsePeople = tagNoAttr "people" $ many parsePerson
inputXml = mconcat
[ "<?xml version=\"1.0\" encoding=\"utf-8\"?>"
, "<people>"
, "  <person age=\"25\" goodAtHaskell=\"yes\">Michael</person>"
, "  <person age=\"2\" goodAtHaskell=\"might become\">Eliezer</person>"
, "</people>"
]
:}

    >>> runConduit $ parseLBS def inputXml .| force "people required" parsePeople
[Person 25 "Michael" "yes",Person 2 "Eliezer" "might become"]
    This module also supports streaming results using yield. This allows parser results to be processed using conduits while a particular parser (e.g. many) is still running. Without using streaming results, you have to wait until the parser finished before you can process the result list. Large XML files might be easier to process by using streaming results. See http://stackoverflow.com/q/21367423/2597135 for a related discussion. 
    >>> import Data.Conduit.List as CL

>>> :{
let parsePeople' :: MonadThrow m => ConduitT Event Person m (Maybe ())
parsePeople' = tagNoAttr "people" $ manyYield parsePerson
:}

    >>> runConduit $ parseLBS def inputXml .| force "people required" parsePeople' .| CL.mapM_ print
Person 25 "Michael" "yes"
Person 2 "Eliezer" "might become"
    Previous versions of this module contained a number of more sophisticated functions written by Aristid Breitkreuz and Dmitry Olshansky. To keep this package simpler, those functions are being moved to a separate package. This note will be updated with the name of the package(s) when available.

  2. data ParseSettings

    xml-conduit Text.XML.Stream.Parse

    No documentation available.

  3. data PositionRange

    xml-conduit Text.XML.Stream.Parse

    No documentation available.

  4. data ParseSettings

    xml-conduit Text.XML.Unresolved

    No documentation available.

  5. type PathsAndQueries = ([Text], Query)

    wai-extra Network.Wai.Middleware.Rewrite

    A tuple of the path sections as [Text] and query parameters as Query. This makes writing type signatures for the conversion function far more pleasant. Note that this uses Query not QueryText to more accurately reflect the paramaters that can be supplied in URLs. It may be safe to treat parameters as text; use the queryToQueryText and queryTextToQuery functions to interconvert.

  6. module Network.Wai.Parse

    Some helpers for parsing data out of a raw WAI Request.

  7. type Param = (ByteString, ByteString)

    wai-extra Network.Wai.Parse

    Post parameter name and value.

  8. ParamNameTooLong :: ByteString -> Int -> RequestParseException

    wai-extra Network.Wai.Parse

    No documentation available.

  9. data ParseRequestBodyOptions

    wai-extra Network.Wai.Parse

    A data structure that describes the behavior of the parseRequestBodyEx function.

  10. newtype PatternMatchFail

    lifted-base Control.Exception.Lifted

    A pattern match failed. The String gives information about the source location of the pattern.

Page 190 of many | Previous | Next