Data.Csv.Conduit

Conduit interface for cassava

Types

data CsvParseError

Constructors

CsvParseError ByteString String

IncrementalError String

Conduits

fromCsv :: (FromRecord a, MonadError CsvParseError m) => DecodeOptions -> HasHeader -> Conduit ByteString m a

Streams parsed records, Errors are not received in the stream but instead after the pipeline is executed, If you want to handle errors as they come and resume, see fromCsvStreamError

fromCsvLiftError :: (FromRecord a, MonadError e m) => (CsvParseError -> e) -> DecodeOptions -> HasHeader -> Conduit ByteString m a

Sometimes your pipeline will involve an error type other than CsvParseError, in which case if you provide a function to project it into your custom error type, you can use this instead of fromCsv

fromNamedCsv :: (FromNamedRecord a, MonadError CsvParseError m) => DecodeOptions -> Conduit ByteString m a

Parses an instance of FromNamedRecord, this conduit drops the Header

Errors are not seen in the pipeline but rather at the end after executing the pipeline, if you want to handle the errors as they occur, try fromNamedCsvStreamError instead.

fromNamedCsvLiftError :: (FromNamedRecord a, MonadError e m) => (CsvParseError -> e) -> DecodeOptions -> Conduit ByteString m a

Sometimes your pipeline will involve an error type other than CsvParseError, in which case if you provide a function to project it into your custom error type, you can use this instead of fromCsv

fromCsvStreamError :: (Monad m, FromRecord a) => DecodeOptions -> HasHeader -> Conduit ByteString m (Either CsvParseError a)

Same as fromCsv but allows for errors to be handled in the pipeline instead

fromNamedCsvStreamError :: (Monad m, FromNamedRecord a) => DecodeOptions -> Conduit ByteString m (Either CsvParseError a)

Like fromNamedCsvStream but allows for errors to be handled in the pipeline itself.

toCsv :: (Monad m, ToRecord a) => EncodeOptions -> Conduit a m ByteString

Streams from csv to text, does not create headers...