aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Track type signature change of lookupModuleInAllPackagesEdward Z. Yang2014-08-051-6/+3
| | | | Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
* Catch mid-line URLs. Fixes #314.Mateusz Kowalczyk2014-07-282-2/+6
|
* Track changes for module reexports.Edward Z. Yang2014-07-251-2/+3
| | | | | | | Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu> Conflicts: src/Haddock/Interface/Create.hs
* Track GHC PackageId to PackageKey renaming.Edward Z. Yang2014-07-219-30/+30
| | | | | | | Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu> Conflicts: src/Haddock/Interface/Create.hs
* Adapt to new definition of HsDecls.TyFamEqnSimon Peyton Jones2014-07-144-16/+26
| | | | | This is a knock-on from the refactoring from Trac #9063. I'll push the corresponding changes to GHC shortly.
* Propagate overloading-mode for instance declarations in haddock (#9242)Iavor S. Diatchki2014-07-011-2/+6
|
* 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-254-37/+51
| | | | | | | | 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-254-10/+14
| | | | | 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-259-6/+274
|
* Update Travis, bump versionMateusz Kowalczyk2014-06-192-1/+3
|
* 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
|
* Don't actually forget to install specified GHC.Mateusz Kowalczyk2014-06-181-0/+1
|
* Travis tweaksMateusz Kowalczyk2014-06-181-1/+5
|
* Remove doctest dependencySimon Hengel2014-06-183-22/+4
| | | | (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
|
* Use Travis with multiple GHC versionsMateusz Kowalczyk2014-06-181-2/+28
| | | | | | | When using HEAD, we build haddock-library directly from repository as a dependency (and thanks to --enable-tests, the tests get ran anyway). In all other cases, we manually run the tests on haddock-library only and don't test the main project.
* 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).
* Enable travis-ci for haddock-librarySimon Hengel2014-06-181-0/+7
|
* Compatibility with older versions of base and bytestringSimon Hengel2014-06-184-3/+21
|
* Update cabal filesMateusz Kowalczyk2014-06-182-3/+4
| | | | | Update repository urls, use subdir property for haddock-library and use a separate versioning scheme for haddock-library in preparation for release.
* Slightly update the readme.Mateusz Kowalczyk2014-06-121-21/+10
| | | | | Style-sheets are no longer a recent thing, dead links, old maintainers, different formats.
* Follow change in patSynSigSimon Peyton Jones2014-06-061-2/+2
|
* Clear up highlighting of identifiers with ‘'’s.Mateusz Kowalczyk2014-06-051-0/+5
|
* Revert "Revert "Accomodate change in PatSyn representation""Mateusz Kowalczyk2014-05-291-1/+1
| | | | | | | This reverts commit e110e6e70e40eed06c06676fd2e62578da01d295. Apparently as per GHC commit ac2796e6ddbd54c5762c53e2fcf29f20ea162fd5 this was actually intended. Embarrasing for me.
* Revert "Accomodate change in PatSyn representation"Mateusz Kowalczyk2014-05-291-1/+1
| | | | | | This reverts commit 57aa591362d7c8ba21285fccd6a958629a422091. I am reverting this because I pushed it to master when it was meant to stay on a wip-branch. Sorry Gergo and everyone who had trouble due to this.
* Accomodate change in PatSyn representationDr. ERDI Gergo2014-05-251-1/+1
|
* Update issue tracker URL for haddock-libraryMateusz Kowalczyk2014-05-141-1/+1
|
* Update issue tracker URLMateusz Kowalczyk2014-05-141-1/+1
|
* Please the GHC build-system.Mateusz Kowalczyk2014-05-141-8/+41
| | | | | | As I can not figure out how to do this properly, if we're in GHC tree, we treat the library as being the same package. If we're not in the tree, we require that the library be installed separately.
* Remove no longer necessary parser error handling.Mateusz Kowalczyk2014-05-065-147/+105
| | | | | We can now drop some Maybe tests and even lets us strip an error handling monad away in a few places.
* 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-0534-907/+841
| | | | | | | | | | 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.
* Prepare modules for parser split.Mateusz Kowalczyk2014-05-0510-169/+206
| | | | | We have to generalise the Doc (now DocH) slightly to remove the dependency on GHC-supplied type.
* Disambiguate ‘die’ in test runners.Mateusz Kowalczyk2014-05-032-2/+2
|
* Replace local `die` by new `System.Exit.die`Herbert Valerio Riedel2014-04-211-5/+1
| | | | | | | | | | | | | Starting with GHC 7.10, System.Exit exports the new `die` which is essentially the same as Haddock.Util.die, so this commit changes Haddock.Util.die to be a simple re-export of System.Exit.die. See also https://ghc.haskell.org/trac/ghc/ticket/9016 for more details. Signed-off-by: Herbert Valerio Riedel <hvr@gnu.org>
* remove Origin flag from LHsBindsLRDr. ERDI Gergo2014-04-131-8/+8
|
* Update CHANGES to follow 2.14.3Mateusz Kowalczyk2014-04-111-0/+4
|
* Ignore version string during HTML tests.Mateusz Kowalczyk2014-04-111-1/+13
|
* Parse identifiers with ^ and ⋆ in them.Mateusz Kowalczyk2014-04-113-1/+164
| | | | Fixes #298.
* We don't actually want unicode hereMateusz Kowalczyk2014-04-111-1/+0
|
* Initialise some new PlatformConstants fieldsMateusz Kowalczyk2014-04-031-0/+2
|
* Enforce strict GHC version in cabal fileMateusz Kowalczyk2014-04-031-2/+2
| | | | | This stops people with 7.6.3 trying to install 2.15.x which clearly won't work. Unfortunately we shipped 2.14.x without realising this.
* Update test cases for GHC bug #8945, Haddock #188Mateusz Kowalczyk2014-04-037-57/+186
| | | | | | | The order of signature groups has been corrected upstream. Here we add a test case and update some existing test-cases to reflect this change. We remove grouped signature in test cases that we can (Minimal, BugDeprecated &c) so that the test is as self-contained as possible.
* Actually bundle extra spec tests in sdistMateusz Kowalczyk2014-04-011-0/+3
|
* Make CHANGES consistent with what's now in 2.14.2Mateusz Kowalczyk2014-04-011-0/+6
|
* Crash when exporting record selectors of data family instancesNiklas Haas2014-03-313-10/+226
| | | | | | | | | | | | | | | | | | | This fixes bug #294. This also fixes a related but never-before-mentioned bug about the display of GADT record selectors with non-polymorphic type signatures. Note: Associated data type constructors fail to show up if nothing is exported that they could be attached to. Exporting any of the data types in the instance head, or the class + data family itself, causes them to show up, but in the absence of either of these, exporting just the associated data type with the constructor itself will result in it being hidden. The only scenario I can come up that would involve this kind of situation involved OverlappingInstances, and even then it can be mitigated by just exporting the class itself, so I'm not going to solve it since the logic would most likely be very complicated.