monad-validate: A monad transformer for data validation.

[ control, library ] [ Propose Tags ]

Provides the ValidateT monad transformer, designed for writing data validations that provide high-quality error reporting without much effort. ValidateT automatically exploits the data dependencies of your program—as encoded implicitly in uses of fmap, <*>, and >>=—to report as many errors as possible upon failure instead of completely aborting at the first one. See Control.Monad.Validate for more information.


[Skip to Readme]
Versions [faq] 1.0.0.0, 1.1.0.0, 1.2.0.0
Change log CHANGELOG.md
Dependencies base (>=4.11 && <5), exceptions (>=0.9 && <1), monad-control (==1.*), mtl, transformers (>=0.5.6), transformers-base (==0.*) [details]
License ISC
Copyright 2019 Hasura
Author Alexis King <lexi.lambda@gmail.com>
Maintainer Alexis King <lexi.lambda@gmail.com>
Revised Revision 1 made by lexi_lambda at Sun Aug 4 11:53:08 UTC 2019
Category Control
Home page https://github.com/hasura/monad-validate#readme
Bug tracker https://github.com/hasura/monad-validate/issues
Source repo head: git clone https://github.com/hasura/monad-validate
Uploaded by lexi_lambda at Sun Aug 4 11:48:43 UTC 2019
Distributions NixOS:1.2.0.0
Downloads 174 total (54 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2019-08-04 [all 2 reports]

Modules

[Index] [Quick Jump]

Downloads

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

For package maintainers and hackage trustees


Readme for monad-validate-1.0.0.0

[back to package description]

monad-validate

A Haskell library providing the ValidateT monad transformer, designed for writing data validations that provide high-quality error reporting without much effort. ValidateT automatically exploits the data dependencies of your program—as encoded implicitly in uses of fmap, <*>, and >>=—to report as many errors as possible upon failure instead of completely aborting at the first one.

See the documentation on Hackage for more information and examples.