hlint-test: Run hlint in test suite

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain]

Allows you to write small hlint test runner; so you will not forget to run hlint before pushing to master.


[Skip to ReadMe]

Properties

Versions0.1.0.0, 0.1.0.1
Change logCHANGES.md
Dependenciesbase (>=4.7 && <5), hlint (>=2.0), hlint-test [details]
LicenseBSD-3-Clause
Copyright2017 Tomáš Janoušek, Jan Šipr
AuthorTomáš Janoušek <tomi@nomi.cz>, Jan Šipr <sipr.jan@gmail.com>
MaintainerJan Šipr <sipr.jan@gmail.com>
Categorytest
Home pagehttps://github.com/Siprj/hlint-test#readme
Bug trackerhttps://github.com/Siprj/hlint-test/issues
Source repositoryhead: git clone https://github.com/Siprj/hlint-test
Executableshlint-test
UploadedFri Dec 29 13:30:12 UTC 2017 by yrid

Modules

Flags

NameDescriptionDefaultType
pedantic

Pass additional warning flags and -Werror to GHC.

DisabledManual

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainers' corner

For package maintainers and hackage trustees


Readme for hlint-test-0.1.0.1

[back to package description]

hlint-test

Build Status Hackage Hackage Dependencies Stackage LTS Stackage Nightly BSD3 License

This package aims to make easy to automatically run hlint as part of unit tests. That means hlint will be run when you execute cabal test or stack test.

How to make it work

Hlint-test package contains GHC preprocessor which will generate the code containing hlint runner. To invoke the preprocessor, create new test and put following line into it:

{-# OPTIONS_GHC -F -pgmF hlint-test #-}

Don't forget to add the test into cabal file (or package.yaml respectively) as separated test runner ;).

Now you can run the test simply by stack test or cabal test.

Hlint options

If you need to you can use the preprocessor macro to pass some additional arguments to the hlint. As it's shown on following line:

{-# OPTIONS_GHC -F -pgmF hlint-test -optF src -optF -r #-}

This will tell hlint to look for source codes only in src directory and to generate html report if some suggestions are found.

Also you can use hlint configuration file too ;).

Example

Simple example of the use can be seen in https://github.com/Siprj/hlint-test-example