monad-validate: A monad transformer for data validation.
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]
Modules
[Index] [Quick Jump]
Downloads
- monad-validate-1.2.0.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
| Versions [RSS] | 1.0.0.0, 1.1.0.0, 1.2.0.0, 1.2.0.1 |
|---|---|
| Change log | CHANGELOG.md |
| Dependencies | base (>=4.12 && <5), exceptions (>=0.9 && <1), monad-control (>=1 && <2), mtl, transformers (>=0.5.6), transformers-base (<1) [details] |
| License | ISC |
| Copyright | 2019 Hasura, 2022 Alexis King |
| Author | Alexis King <lexi.lambda@gmail.com> |
| Maintainer | Alexis King <lexi.lambda@gmail.com> |
| Category | Control |
| Home page | https://github.com/lexi-lambda/monad-validate |
| Bug tracker | https://github.com/lexi-lambda/monad-validate/issues |
| Source repo | head: git clone https://github.com/lexi-lambda/monad-validate |
| Uploaded | by lexi_lambda at 2022-07-05T07:45:23Z |
| Distributions | NixOS:1.2.0.1 |
| Reverse Dependencies | 7 direct, 3 indirect [details] |
| Downloads | 4359 total (51 in the last 30 days) |
| Rating | 1.25 (votes: 1) [estimated by Bayesian average] |
| Your Rating | |
| Status | Docs available [build log] Last success reported on 2022-07-05 [all 1 reports] |
Readme for monad-validate-1.2.0.1
[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.