aboutsummaryrefslogtreecommitdiff
path: root/html-test/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Add basic HTML test case for checking instance specialization.Łukasz Hanuszczak2015-08-211-0/+36
|
* Rename advanced types test case and accept new output.Łukasz Hanuszczak2015-08-061-1/+3
|
* Extend advanced types test case with other examples.Łukasz Hanuszczak2015-08-061-0/+14
|
* Delete trailing whitespaceMateusz Kowalczyk2015-07-071-1/+1
|
* Build executable with '-threaded' (fixes #399)Emanuel Borsboom2015-06-122-0/+23
|
* Add simple test case for arbitrary-depth list nesting.Łukasz Hanuszczak2015-05-271-0/+15
|
* Do not insert anchor for section headings in contents boxwatashi2015-04-261-0/+12
|
* Test for anchor defaultingMateusz Kowalczyk2015-03-273-12/+10
| | | | | | | | | I delete the old tests because it turns out that: * test runner would never put them in scope of each other even with imports so just one would suffice * test runner actually needed some hacking to keep links so in the end we would end up with no anchors making them useless
* support GHC 7.10: no Safe-Inferred, Foldable instancejpmoresmau2015-01-221-0/+1
|
* Allow the parser to spit out meta-infoMateusz Kowalczyk2014-12-101-0/+29
| | | | | | | | | | | | | | | 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.
* Fix re-exports of built-in type familiesMateusz Kowalczyk2014-11-041-0/+4
| | | | Fixes #310
* Experimental support for collapsable headersMateusz Kowalczyk2014-10-291-0/+26
| | | | Closes #335
* Omit unnecessary foralls and fix #315Niklas Haas2014-08-241-1/+22
| | | | This also fixes #86.
* Stop testing #188.Mateusz Kowalczyk2014-08-151-7/+0
| | | | | | 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/+37
| | | | | | 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.
* Fix anchors. Closes #308.Mateusz Kowalczyk2014-06-252-0/+38
|
* Parse identifiers with ^ and ⋆ in them.Mateusz Kowalczyk2014-04-111-0/+22
| | | | Fixes #298.
* We don't actually want unicode hereMateusz Kowalczyk2014-04-111-1/+0
|
* Update test cases for GHC bug #8945, Haddock #188Mateusz Kowalczyk2014-04-033-9/+37
| | | | | | | 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/+37
| | | | | | | | | | | | | | | | | | | 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/+28
| | | | Fixes #201.
* Print kind signatures on GADTsMateusz Kowalczyk2014-03-311-0/+15
|
* Fix issue #281Niklas Haas2014-03-151-5/+11
| | | | | | | | | 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-151-0/+40
| | | | | | | 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.
* Display minimal complete definitions for type classesNiklas Haas2014-03-131-0/+1
| | | | | | | | | 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-8/+24
| | | | | | 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-2/+2
|
* Filter family instances of hidden typesNiklas Haas2014-03-111-0/+8
| | | | | Currently, this check does not extend to hidden right hand sides, although it probably should hide them in that case.
* Group similar fixities togetherNiklas Haas2014-03-091-1/+9
| | | | | Identical fixities declared for the same line should now render using syntax like: infix 4 <, >=, >, <=
* Render fixity informationNiklas Haas2014-03-081-0/+56
| | | | | | 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/+11
| | | | | | | | 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-2/+5
| | | | | | | 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-9/+16
| | | | | | | 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/+10
| | | | | | 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)
* Strip a single leading space from bird tracks (#201)Niklas Haas2014-02-221-0/+6
| | | | | | | | | | | | | | | | | | | | 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-1/+12
| | | | | | | 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/+22
| | | | | | | 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-2/+12
| | | | | | | 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-112-18/+70
| | | | | | | | 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>
* Update testsMateusz Kowalczyk2014-01-301-1/+1
| | | | | This updates tests due to Haddock Trac #271 fix and due to removal of TypeHoles as an extension from GHC.
* Allow for nesting of paragraphs under lists.Mateusz Kowalczyk2014-01-121-0/+115
| | | | | | | | | | | | | | | | | 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
* Bump interface versionMateusz Kowalczyk2014-01-121-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were some breaking changes over the last few patches so we bump the interface version. This causes a big problem with testing: 1. To generate cross package docs, we first need to generate docs for the package used. 2. To generate package docs with new interface version, we need to use Haddock which has the version bumped. 3. To get Haddock with the version bump, we first need to test cross package docs 4. GOTO 1 So the problem is the chicken and the egg problem. It seems that the only solution would be to generate some interface files on the fly but it is non-trivial. To run this test, you'll have to: * build Haddock without the test (make sure everything else passes) * rebuild the packages used in the test with your shiny new binary making sure they are visible to Haddock * remove the ‘_hidden’ suffix and re-run the tests Note: because the packages currently used for this test are those provided by GHC, it's probably non-trivial to just re-build them. Preferably something less tedious to rebuild should be used and something that is not subject to change.
* Per-module extension flags and language listing.Mateusz Kowalczyk2014-01-121-0/+7
| | | | | | | | | | | | | 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/+9
| | | | | | | Conflicts: src/Haddock/Backends/Hoogle.hs src/Haddock/Interface/Rename.hs src/Haddock/Parser.hs
* Don't append newline to parseString inputSimon Hengel2014-01-125-29/+32
| | | | We also check that we have parsed everything with endOfInput.
* One pass parser and tests.Mateusz Kowalczyk2014-01-123-12/+7
| | | | | | | | 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.
* Fixes #253Mateusz Kowalczyk2013-09-022-0/+12
|
* Using new syntax in html-test/src/GADTRecords.hs.Kazu Yamamoto2013-02-071-5/+4
|
* Move source files for HTML tests to html-test/srcSimon Hengel2012-10-1557-0/+1123
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-18 03:47:39 +0000