aboutsummaryrefslogtreecommitdiff
path: root/haddock-library
Commit message (Collapse)AuthorAgeFilesLines
...
* Bump haddock-library to 1.1.0 for releaseMateusz Kowalczyk2014-06-251-1/+1
|
* Don't mangle append order for nested lists.Mateusz Kowalczyk2014-06-252-22/+10
| | | | | | | | The benefit of this is that the ‘top-level’ element of such lists is properly wrapped in <p> tags so any CSS working with these will be applied properly. It also just makes more sense. Pointed out at jgm/pandoc#1346.
* Drop DocParagraph from front of headersMateusz Kowalczyk2014-06-252-6/+10
| | | | | I can not remember why they were wrapped in paragraphs to begin with and it seems unnecessary now that I test it. Closes #307.
* Fix anchors. Closes #308.Mateusz Kowalczyk2014-06-252-3/+21
|
* Update Travis, bump versionMateusz Kowalczyk2014-06-191-1/+1
|
* Fixed haddock warnings.John MacFarlane2014-06-181-6/+4
|
* Removed reliance on LambdaCase (which breaks build with ghc 7.4).John MacFarlane2014-06-181-3/+3
|
* Remove doctest dependencySimon Hengel2014-06-182-19/+0
| | | | (so that we can use haddock-library with doctest)
* Use doctest to check examples in documentationSimon Hengel2014-06-183-0/+22
|
* Comment improvements + few words in cabal fileMateusz Kowalczyk2014-06-182-11/+32
|
* haddock-library: Use -Wall for specsSimon Hengel2014-06-181-0/+2
|
* haddock-library: Do not depend on haddock-library in test suiteSimon Hengel2014-06-181-2/+0
| | | | | I think you either add src to hs-source-dirs or the library to build-depends. But doing both does not make sense (AFAICT).
* Compatibility with older versions of base and bytestringSimon Hengel2014-06-184-3/+21
|
* Update cabal filesMateusz Kowalczyk2014-06-181-2/+3
| | | | | Update repository urls, use subdir property for haddock-library and use a separate versioning scheme for haddock-library in preparation for release.
* Update issue tracker URL for haddock-libraryMateusz Kowalczyk2014-05-141-1/+1
|
* Move out Show and Eq instances to TypesMateusz Kowalczyk2014-05-052-8/+8
| | | | They are much more useful to the users here.
* Move parser + parser tests out to own package.Mateusz Kowalczyk2014-05-0522-0/+3686
We move some types out that are necessary as well and then re-export and specialise them in the core Haddock. Reason for moving out spec tests is that if we're working on the parser, we can simply work on that and we can ignore the rest of Haddock. The downside is that it's a little inconvenient if at the end of the day we want to see that everything passes.