aboutsummaryrefslogtreecommitdiff
path: root/haddock-library/src/Documentation
Commit message (Collapse)AuthorAgeFilesLines
...
* Create simple method for indentation parsing.Łukasz Hanuszczak2015-05-271-0/+9
|
* Filter '\r' from comments due to Windows problems.Vincent Berthoux2015-01-221-2/+3
| | | | | On Windows this was causing newline to be rendered twice in code blocks. Closes #359, fixes #356.
* Only keep one Version instead of blindly appendingMateusz Kowalczyk2014-12-172-10/+17
|
* Disambiguate string-literalsHerbert Valerio Riedel2014-12-121-4/+4
| | | | | | | | GHC fails type-inference with `OverloadedStrings` + `Data.Foldable.elem` otherwise. Conflicts: haddock-library/src/Documentation/Haddock/Parser.hs
* Update doctest parts of commentsMateusz Kowalczyk2014-12-101-18/+22
|
* Allow the parser to spit out meta-infoMateusz Kowalczyk2014-12-103-3/+43
| | | | | | | | | | | | | | | Currently we only use it only for ‘since’ annotations but with these patches it should be fairly simple to add new attributes if we wish to. Closes #26. It seems to work fine but due to 7.10 rush I don't have the chance to do more exhaustive testing right now. The way the meta is output (emphasis at the end of the whole comment) is fairly arbitrary and subject to bikeshedding. Note that this makes test for Bug310 fail due to interface version bump: it can't find the docs for base with this interface version so it fails. There is not much we can do to help this because it tests for ’built-in’ identifier, not something we can provide ourselves.
* (wip) Add support for @since (closes #26)Simon Hengel2014-11-163-12/+49
|
* State intention rather than implementation details in Haddock commentSimon Hengel2014-11-161-1/+1
|
* newtype-wrap parser monadSimon Hengel2014-11-083-2/+130
|
* Minor code simplificationSimon Hengel2014-11-081-4/+3
|
* Fix parsing of identifiers written in infix wayMateusz Kowalczyk2014-11-041-11/+12
|
* Allow an optional colon after the closing bracket of definition listsSimon Hengel2014-11-031-1/+1
| | | | | This is to disambiguate them from markdown links and will be require with a future release.
* Add support for markdown imagesSimon Hengel2014-11-031-2/+10
|
* Allow markdown links at the beginning of a paragraphSimon Hengel2014-11-031-2/+18
|
* Add support for markdown links (closes #336)Simon Hengel2014-11-032-10/+30
|
* parser: Try to parse definition lists right before text paragraphsSimon Hengel2014-11-031-1/+1
|
* Minor refactoringSimon Hengel2014-11-031-22/+28
|
* Remove unused language extensionsSimon Hengel2014-11-031-4/+0
|
* Derive more instancesSimon Hengel2014-11-031-8/+1
|
* Get rid of StandaloneDerivingSimon Hengel2014-11-031-10/+3
|
* Fix #313 by doing some list munging.Mateusz Kowalczyk2014-08-152-20/+18
| | | | | | I get rid of the Monoid instance because we weren't satisfying the laws. Convenience of having <> didn't outweigh the shock-factor of having it behave badly.
* Catch mid-line URLs. Fixes #314.Mateusz Kowalczyk2014-07-281-2/+2
|
* Don't mangle append order for nested lists.Mateusz Kowalczyk2014-06-251-14/+2
| | | | | | | | 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-251-1/+6
| | | | | 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-251-3/+8
|
* 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
|
* Use doctest to check examples in documentationSimon Hengel2014-06-181-0/+3
|
* Comment improvements + few words in cabal fileMateusz Kowalczyk2014-06-181-9/+28
|
* Compatibility with older versions of base and bytestringSimon Hengel2014-06-182-2/+19
|
* Move out Show and Eq instances to TypesMateusz Kowalczyk2014-05-051-0/+6
| | | | They are much more useful to the users here.
* Move parser + parser tests out to own package.Mateusz Kowalczyk2014-05-055-0/+739
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.