| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
I think thst CSS was meant only to deal with fields and the
effect on bullets was accidental.
Fixes #926.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here's these changes are supposed to do:
* put the synopsis back on the right side
* properly have it on the edge of the screen on wide screens
* adjust the background of the synopsis to match the button
(otherwise the grey blends in with what is underneath)
* get rid of the dotted purple line
* the synopsis contents are now scrollable even when in wide
screens (this has been a long-standing bug)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes #810. Looks like things were broken during the quickjump
refactor of the JS.
For the (git) record: I do not think the style switcher is a good idea.
I'm fixing it for the same reason @mzero added it; as an answer to
"rumblings from some that they didn't want their pixels changed on bit"
|
|
|
|
|
| |
This was done via `npm audit fix`. I think this fixes #903 along with
some more serious vulnerabilities that nobody seems to have noticed.
|
| |
|
|
|
|
|
|
|
| |
The current html generator of this branch wraps the package-header
caption as a div, which does not work (without style adjustments) with
the old themes. Changing it from div to span does the trick, without
needing to adjust the old stylesheets.
|
|
|
|
|
| |
- Fix and improve spacing
- Improve colors and borders
|
| |
|
|
|
|
|
|
|
| |
- Update link colors to hackage scheme
- Tune spacing between content elements
- Update footer style
- Fix and improve code blocks identation
|
| |
|
|
|
|
| |
Also migrate some general text related changes from hackage.
|
| |
|
|
|
|
|
| |
Reported and described here:
https://github.com/haskell/haddock/pull/721#issuecomment-374668869
|
|
|
|
|
|
|
| |
The min and max width triggers have the same values,
which caused the style resolution to take an intersection of
both style declarations when the screen resolution had the size
of the limts (say 1280px), causing an odd behaviour and look.
|
|
|
|
|
|
| |
Bring in some adjustments made to hackage:
- link colors
- page header show everything when package title is too long
|
|
|
|
|
|
|
| |
- Reduce font size
- Improve space between and within code blocks
- Improve alignments
- Improve spacing within sub-blocks
|
|
|
|
|
| |
When the synopsis is longer than the screen, you can’t see its end
and you can't scroll down either, making the content unreachable.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Darken text color like done for hackage
- Move synopsis to left side
- Make table of contents stick to the left on wide screens
- Wrap links to avoid page overflow
- Improve expand/collapse buttons
- Fix issue with content size on mobile devices
- Fix issue with font-size on landscape mode
- Increase width of the content
- Change colors of table of contents and synopsis
- Etc
|
|
|
|
|
| |
This solves an issue reported about the content looking
incredibly small on mobile devices.
|
|
|
|
|
| |
There was too much space between code blocks as pointed out by
reviewers.
|
|
|
|
|
| |
- Use CSS3 instead of loading pictures to show "+" and "-" symbols
- Drop redundant code
|
|
|
|
|
| |
This supports the expected responsive menu design, where the
package name appears above the menu links.
|
|
|
|
|
|
|
|
|
| |
Several things are addressed here:
- better responsive behaviour on the header
- better space usage
- consistent colors overall
- other nit PR comments
|
|
|
|
|
|
| |
- It makes small screens taking more space than larger ones
- fixes a few issues present in small screens currently
- make it look good across different screen sizes.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
These changes include:
- use latest Haskell's logo colors
- decrease #content width to improve readability
- use nicer font
- improve sizes and distances
|
|
|
|
| |
And make it the default theme.
|
|
|
|
| |
This version will accompany ghc-8.6.2
|
|
|
|
|
|
|
|
|
|
|
| |
* Output pattern synonyms in Hoogle backend
We were previously weren't outputting _any_ pattern synonyms, bundled or
not. Now, we output both.
Fixes #946.
* Update changelog
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Support for type families in LaTeX
The code is ported over from the XHTML backend.
* Refactor XHTML and LaTeX family handling
This is mostly a consolidation effort: stripping extra exports,
inlining some short definitions, and trying to make the backends
match.
The LaTeX backend now has preliminary support for data families,
although the only the data instance head is printed (not the actual constructors).
Both backends also now use "newtype" for newtype data family
instances.
* Add some tests
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Make --package-version optional for --hoogle generation
* Import mkVersion
* It's makeVersion not mkVersion
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Steps to reproduce and the error message
====
```
> stack haddock basement
... snip ...
Warning: 'A' is out of scope.
Warning: 'haddock: internal error: <stdout>: commitBuffer: invalid argument (invalid character)
```
Environment
====
OS: Windows 10 ver. 1709
haddock: [HEAD of ghc-8.4 when I reproduce the error](https://github.com/haskell/haddock/commit/532b209d127e4cecdbf7e9e3dcf4f653a5605b5a). (I had to use this version to avoid another probrem already fixed in HEAD)
GHC: 8.4.3
stack: Version 1.7.1, Git revision 681c800873816c022739ca7ed14755e85a579565 (5807 commits) x86_64 hpack-0.28.2
Related pull request
====
https://github.com/haskell/haddock/pull/566
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The problem manifests itself in instances that are defined in
modules other than the module where the class is defined. The fix
is just to thread through the 'Module' of the instance further
along.
Since orphan instances appear to already have been working, I didn't
do anything there.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Preserve docs on type family instances
The only problem was that the instance location was slightly off
for type family instances.
* Accept output
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* tyThingToLHsDecls: Preserve type synonyms that contain a forall
Fixes #879.
* Add Note [Invariant: Never expand type synonyms]
* Clarify Note [Invariant: Never expand type synonyms]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Avoid line breaks due to line length in Hoogle
Hoogle operates in a line-oriented fashion, so we should avoid ever
breaking due to long lines.
One way of doing this non-intrusively is to modify the 'DynFlags' that
are threaded through the 'Hoogle' module (note this is anyways only
passed through for use in the various 'showSDoc' functions).
* Amend test case
|
| |
| |
| |
| | |
This exports fixities for more things, including class methods and
type-level operators.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Renamer: Warn about ambiguous identifiers
Example:
Warning: 'elem' is ambiguous. It is defined
* in ‘Data.Foldable’
* at /home/simon/tmp/hdk/src/Lib.hs:7:1
You may be able to disambiguate the identifier by qualifying it or
by hiding some imports.
Defaulting to 'elem' defined at /home/simon/tmp/hdk/src/Lib.hs:7:1
Fixes #830.
* Deduplicate warnings
Fixes #832.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
'spanToNewline' is used to help break apart the source into lines which
can then be partioned into CPP and non-CPP chunks. It is important that
'spanToNewline' not break apart tokens, so it needs to properly handle
things like
* block comments, possibly nested
* string literals, possibly multi-line
* CPP macros, possibly multi-line
String literals in particular were not being properly handled. The fix
is to to fall back in 'Text.Read.lex' to help lex things that are not
comments.
Fixes #837.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Fix minimal pragma handling
Class declarations contain 'ClassOpSig' not 'Typesig'. This should fix #834.
* Accept html-test output
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Since the hyperlinker backend now relies on the GHC tokenizer, something
like 'Bar.Baz.foo' already gets bunched together into one token (as
opposed to being spread across 'Bar', '.', 'Baz', '.', and 'foo').
|
| |
| |
| | |
This prevents spurious lines from appearing in the final output.
|