aboutsummaryrefslogtreecommitdiff
path: root/html-test/ref
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix re-exports of built-in type familiesMateusz Kowalczyk2014-11-041-0/+89
| | | | Fixes #310
* Experimental support for collapsable headersMateusz Kowalczyk2014-10-291-0/+125
| | | | Closes #335
* Omit unnecessary foralls and fix #315Niklas Haas2014-08-241-3/+117
| | | | This also fixes #86.
* Fix extra whitespace on signatures and update all test casesNiklas Haas2014-08-2433-108/+200
| | | | | This was long overdue, now running ./accept.lhs on a clean test from master will not generate a bunch of changes.
* Stop testing #188.Mateusz Kowalczyk2014-08-152-89/+8
| | | | | | Because the change is in GHC 7.9 and we now work against 7.8.3, this test no longer makes sense. We revert it until 7.10 becomes the standard version. If anything, there should be a test for this in GHC itself.
* Fix #313 by doing some list munging.Mateusz Kowalczyk2014-08-151-0/+132
| | | | | | 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.
* Don't mangle append order for nested lists.Mateusz Kowalczyk2014-06-251-15/+39
| | | | | | | | 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-4/+2
| | | | | 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-0/+202
|
* Parse identifiers with ^ and ⋆ in them.Mateusz Kowalczyk2014-04-111-0/+133
| | | | Fixes #298.
* Update test cases for GHC bug #8945, Haddock #188Mateusz Kowalczyk2014-04-034-48/+149
| | | | | | | 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.
* Crash when exporting record selectors of data family instancesNiklas Haas2014-03-311-0/+165
| | | | | | | | | | | | | | | | | | | 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.
* Drop leading whitespace in @-style blocks.Mateusz Kowalczyk2014-03-311-0/+102
| | | | Fixes #201.
* Print kind signatures on GADTsMateusz Kowalczyk2014-03-312-1/+136
|
* Fix issue #281Niklas Haas2014-03-151-81/+223
| | | | | | | | | This is a regression from the data family instances change. Data instances are now distinguished from regular lists by usage of the new class "inst", and the style has been updated to only apply to those. I've also updated the appropriate test case to test this a bit better, including GADT instances with GADT-style records.
* Hide minimal definition for only-method classesNiklas Haas2014-03-154-40/+0
| | | | | | | Previously this was not covered by the All xs check since here it is not actually an All, rather a single Var n. This also adds the previously missing html-test/src/Minimal.hs.
* Strip links from recently added html testsNiklas Haas2014-03-136-217/+217
| | | | These were accidentally left there when the tests were originally added
* Display minimal complete definitions for type classesNiklas Haas2014-03-135-0/+319
| | | | | | | | | This corresponds to the new {-# MINIMAL #-} pragma present in GHC 7.8+. I also cleaned up some of the places in which ExportDecl is used to make adding fields easier in the future. Lots of test cases have been updated since they now render with minimality information.
* Hide RHS of TFs with non-exported right hand sidesNiklas Haas2014-03-131-24/+68
| | | | | | Not sure what to do about data families yet, since technically it would not make a lot of sense to display constructors that cannot be used by the user.
* Fix up some whitespaceMateusz Kowalczyk2014-03-111-1/+1
|
* Bump version to 2.15.0Mateusz Kowalczyk2014-03-1164-64/+64
|
* Update appearance of fixity annotationsNiklas Haas2014-03-112-50/+103
| | | | | | | This moves them in-line with their corresponding lines, similar to a presentation envision by @hvr and described in #ghc. Redundant operator names are also omitted when no ambiguity is present.
* Group similar fixities togetherNiklas Haas2014-03-091-1/+32
| | | | | Identical fixities declared for the same line should now render using syntax like: infix 4 <, >=, >, <=
* Render fixity informationNiklas Haas2014-03-082-2/+383
| | | | | | Affects functions, type synonyms, type families, class names, data type names, constructors, data families, associated TFs/DFs, type synonyms, pattern synonyms and everything else I could think of.
* Change rendering of duplicate record field docsMateusz Kowalczyk2014-02-271-0/+179
| | | | | | | | See Haddock Trac #195. We now change this behaviour to only rendering the documentation attached to the first instance of a duplicate field. Perhaps we could improve this by rendering the first instance that has documentation attached to it but for now, we'll stick with this.
* Add RankNTypes test case to ImplicitParams.hsNiklas Haas2014-02-231-0/+22
| | | | | | | This test actually tests what #260 originally reported - I omitted the RankNTypes scenario from the original fix because I realized it's not relevant to the underlying issue and indeed, this renders as intended now. Still good to have more tests.
* Lower precedence of equality constraintsNiklas Haas2014-02-231-60/+50
| | | | | | | This drops them to the new precedence pREC_CTX, which makes single eqaulity constraints show up as (a ~ b) => ty, in line with GHC's rendering. Additional tests added to make sure other type operators render as intended. Current behavior matches GHC
* Make ImplicitParams render correctly (#260)Niklas Haas2014-02-231-0/+89
| | | | | | This introduces a new precedence level for single contexts (because implicit param contexts always need parens around them, but other types of contexts don't necessarily, even when alone)
* Update test case for lifted GADT type renderingMateusz Kowalczyk2014-02-231-1/+1
| | | | | | The parsing of these seems to have been fixed by GHC folk and it now renders differently. IMHO it now renders in a better way so I'm updating the test to reflect this.
* Strip a single leading space from bird tracks (#201)Niklas Haas2014-02-223-18/+24
| | | | | | | | | | | | | | | | | | | | This makes bird tracks in the form > foo > bar > bat parse as if they had been written as >foo >bar >bat ie. without the leading whitespace in front of every line. Ideally we also want to look into how leading whitespace affects code blocks written using the @ @ syntax, which are currently unaffected by this patch.
* Add test case for inter-module type/data family instancesNiklas Haas2014-02-152-0/+100
| | | | | | | These should show up in every place where the class is visible, and indeed they do right now. Signed-off-by: Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>
* Add test case for PatternSynonymsnand2014-02-111-0/+241
| | | | | | | This just tests various stuff including poly-kinded patterns and operator patterns to make sure the rendering isn't broken. Signed-off-by: Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>
* Improve display of poly-kinded type operatorsnand2014-02-111-66/+226
| | | | | | | This now displays them as (==) k a b c ... to mirror GHC's behavior, instead of the old (k == a) b c ... which was just wrong. Signed-off-by: Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>
* Add support for type/data familiesnand2014-02-113-79/+727
| | | | | | | | This adds support for type/data families with their respective instances, as well as closed type families and associated type/data families. Signed-off-by: Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk>
* Correct whitespace in ‘hidden’ test for <+> changeMateusz Kowalczyk2014-01-301-4/+4
|
* Handle infix vs prefix names correctly everywhere, by explicitly specifying ↵Dr. ERDI Gergo2014-01-311-3/+3
| | | | | | the context The basic idea is that "a" and "+" are either pretty-printed as "a" and "(+)" or "`a`" and "+"
* Update testsMateusz Kowalczyk2014-01-302-2/+2
| | | | | This updates tests due to Haddock Trac #271 fix and due to removal of TypeHoles as an extension from GHC.
* <+>: Don't insert a space when concatenating empty nodesDr. ERDI Gergo2014-01-3123-224/+224
|
* Allow for nesting of paragraphs under lists.Mateusz Kowalczyk2014-01-125-20/+298
| | | | | | | | | | | | | | | | | The nesting rules are similar to Markdown's with the exception that we can not simply indent the first line of a hard wrapped indented paragraph and have it treated as if it was fully indented. The reason is differences in markup as some of our constructs care about whitespace while others just swallow everything up so it's just a lot easier to not bother with it rather than making arbitrary rules. Note that we now drop trailing for string entities inside of lists. They weren't needed and it makes the output look uniform whether we use a single or double newline between list elements. Conflicts: src/Haddock/Parser.hs test/Haddock/ParserSpec.hs
* Per-module extension flags and language listing.Mateusz Kowalczyk2014-01-121-0/+89
| | | | | | | | | | | | | Any extensions that are not enabled by a used language (Haskell2010 &c) will be shown. Furthermore, any implicitly enabled are also going to be shown. While we could eliminate this either by using the GHC API or a dirty hack, I opted not to: if a user doesn't want the implied flags to show, they are recommended to use enable extensions more carefully or individually. Perhaps this will encourage users to not enable the most powerful flags needlessly. Enabled with show-extensions. Conflicts: src/Haddock/InterfaceFile.hs
* Support for bold.Mateusz Kowalczyk2014-01-121-0/+101
| | | | | | | Conflicts: src/Haddock/Backends/Hoogle.hs src/Haddock/Interface/Rename.hs src/Haddock/Parser.hs
* Update acceptance testsSimon Hengel2014-01-121-2/+8
|
* Fix totality, unicode, examples, paragraph parsingSimon Hengel2014-01-1242-393/+201
| | | | | | | | Also simplify specs and parsers while we're at it. Some parsers were made more generic. This commit is a part of GHC pre-merge squash, email fuuzetsu@fuuzetsu.co.uk if you need the full commit history.
* Don't append newline to parseString inputSimon Hengel2014-01-1256-293/+175
| | | | We also check that we have parsed everything with endOfInput.
* One pass parser and tests.Mateusz Kowalczyk2014-01-121-26/+36
| | | | | | | | We remove the HTML test as it is no longer necessary. We cover the test case in spec tests and other HTML tests but keeping this around fails: this is because the new parser has different semantics there. In fact, I suspect the original behaviour was a bug that wasn't caught/fixed but simply included as-is during the testing.
* Bump versionSimon Hengel2013-11-1056-56/+56
|
* Update HTML testsSimon Hengel2013-11-094-0/+275
|
* Update tests.David Waern2013-08-091-4/+16
|
* Fix failing testSimon Hengel2013-07-081-2/+2
|
* Fix failing testSimon Hengel2013-07-081-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-16 08:14:48 +0000