Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Update doctest parts of comments | Mateusz Kowalczyk | 2014-12-10 | 1 | -18/+22 |
| | |||||
* | Allow the parser to spit out meta-info | Mateusz Kowalczyk | 2014-12-10 | 1 | -2/+4 |
| | | | | | | | | | | | | | | | 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 Hengel | 2014-11-16 | 1 | -6/+20 |
| | |||||
* | State intention rather than implementation details in Haddock comment | Simon Hengel | 2014-11-16 | 1 | -1/+1 |
| | |||||
* | newtype-wrap parser monad | Simon Hengel | 2014-11-08 | 1 | -1/+1 |
| | |||||
* | Minor code simplification | Simon Hengel | 2014-11-08 | 1 | -4/+3 |
| | |||||
* | Fix parsing of identifiers written in infix way | Mateusz Kowalczyk | 2014-11-04 | 1 | -11/+12 |
| | |||||
* | Allow an optional colon after the closing bracket of definition lists | Simon Hengel | 2014-11-03 | 1 | -1/+1 |
| | | | | | This is to disambiguate them from markdown links and will be require with a future release. | ||||
* | Add support for markdown images | Simon Hengel | 2014-11-03 | 1 | -2/+10 |
| | |||||
* | Allow markdown links at the beginning of a paragraph | Simon Hengel | 2014-11-03 | 1 | -2/+18 |
| | |||||
* | Add support for markdown links (closes #336) | Simon Hengel | 2014-11-03 | 1 | -2/+20 |
| | |||||
* | parser: Try to parse definition lists right before text paragraphs | Simon Hengel | 2014-11-03 | 1 | -1/+1 |
| | |||||
* | Minor refactoring | Simon Hengel | 2014-11-03 | 1 | -22/+28 |
| | |||||
* | Remove unused language extensions | Simon Hengel | 2014-11-03 | 1 | -4/+0 |
| | |||||
* | Fix #313 by doing some list munging. | Mateusz Kowalczyk | 2014-08-15 | 1 | -13/+13 |
| | | | | | | 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 Kowalczyk | 2014-07-28 | 1 | -2/+2 |
| | |||||
* | Don't mangle append order for nested lists. | Mateusz Kowalczyk | 2014-06-25 | 1 | -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 headers | Mateusz Kowalczyk | 2014-06-25 | 1 | -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 Kowalczyk | 2014-06-25 | 1 | -3/+8 |
| | |||||
* | Fixed haddock warnings. | John MacFarlane | 2014-06-18 | 1 | -6/+4 |
| | |||||
* | Removed reliance on LambdaCase (which breaks build with ghc 7.4). | John MacFarlane | 2014-06-18 | 1 | -3/+3 |
| | |||||
* | Use doctest to check examples in documentation | Simon Hengel | 2014-06-18 | 1 | -0/+3 |
| | |||||
* | Comment improvements + few words in cabal file | Mateusz Kowalczyk | 2014-06-18 | 1 | -9/+28 |
| | |||||
* | Compatibility with older versions of base and bytestring | Simon Hengel | 2014-06-18 | 1 | -1/+1 |
| | |||||
* | Move parser + parser tests out to own package. | Mateusz Kowalczyk | 2014-05-05 | 1 | -0/+474 |
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. |