aboutsummaryrefslogtreecommitdiff
path: root/html-test
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix up some whitespaceMateusz Kowalczyk2014-03-112-3/+3
|
* Bump version to 2.15.0Mateusz Kowalczyk2014-03-1164-64/+64
|
* 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.
* 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-092-2/+41
| | | | | Identical fixities declared for the same line should now render using syntax like: infix 4 <, >=, >, <=
* Render fixity informationNiklas Haas2014-03-083-2/+439
| | | | | | 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-272-0/+190
| | | | | | | | 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-232-2/+27
| | | | | | | 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-232-69/+66
| | | | | | | 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-232-0/+99
| | | | | | 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-224-18/+30
| | | | | | | | | | | | | | | | | | | | 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-154-1/+112
| | | | | | | 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-112-0/+263
| | | | | | | 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-112-68/+238
| | | | | | | 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-115-97/+797
| | | | | | | | 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-303-3/+3
| | | | | 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-126-20/+413
| | | | | | | | | | | | | | | | | 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-122-0/+96
| | | | | | | | | | | | | 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-122-0/+110
| | | | | | | 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-1262-326/+224
| | | | We also check that we have parsed everything with endOfInput.
* One pass parser and tests.Mateusz Kowalczyk2014-01-124-38/+43
| | | | | | | | 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
|
* Fixes #253Mateusz Kowalczyk2013-09-022-0/+12
|
* Update tests.David Waern2013-08-091-4/+16
|
* Fix failing testSimon Hengel2013-07-081-2/+2
|
* Fix failing testSimon Hengel2013-07-081-1/+1
|
* Fix broken testSimon Hengel2013-06-011-3/+3
|
* Workaround for a failing build with --enable-tests.Mateusz Kowalczyk2013-06-011-1/+1
|
* Using new syntax in html-test/src/GADTRecords.hs.Kazu Yamamoto2013-02-071-5/+4
|
* Bump versionSimon Hengel2012-12-0754-54/+54
|
* Use markdown for html-test/READMESimon Hengel2012-10-181-7/+10
|
* Update html-test/READMESimon Hengel2012-10-181-2/+2
|
* Adapt output directory for HTML testsSimon Hengel2012-10-152-4/+4
|
* Move source files for HTML tests to html-test/srcSimon Hengel2012-10-1559-2/+2
|
* Rename html-test/runtests.lhs to html-test/run.lhsSimon Hengel2012-10-151-0/+0
|
* Adapt accept.lhs, so that it ignores more index filesSimon Hengel2012-10-151-7/+7
|
* Add test case for "spurious superclass constraints bug"Simon Hengel2012-10-153-0/+191
|
* Make test management scripts more robustSimon Hengel2012-10-153-13/+22
| | | | | | | * They are now independent from the current directory, and hence can be called from everywhere * On UNIX/Linux they can now be run as scripts
* Copy css, images, etc. on acceptSimon Hengel2012-10-157-15/+906
|
* Move HTML reference renderings to /html-test/ref/Simon Hengel2012-10-15109-5/+5
|
* Move HTML tests to directory /html-test/Simon Hengel2012-10-15166-0/+12847
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-11 10:00:45 +0000