aboutsummaryrefslogtreecommitdiff
path: root/haddock-library/fixtures/examples/list-blocks2.parsed
diff options
context:
space:
mode:
authorOleg Grenrus <oleg.grenrus@iki.fi>2019-02-04 18:44:25 +0200
committerAlec Theriault <alec.theriault@gmail.com>2019-02-04 08:44:25 -0800
commitcacd245a5e0a0f2e14d4ed34e877835fdef3367f (patch)
treed29e2dbdea36129720b7e8df9e9a007e539b0a4b /haddock-library/fixtures/examples/list-blocks2.parsed
parent032ff0dd3411f66131854c4314b9f00c8540fd10 (diff)
Make a fixture of weird parsing of lists (#997)
The second example is interesting. If there's a list directly after the header, and that list has deeper structure, the parser is confused: It finds two lists: - One with the first nested element, - everything after it I'm not trying to fix this, as I'm not even sure this is a bug, and not a feature.
Diffstat (limited to 'haddock-library/fixtures/examples/list-blocks2.parsed')
-rw-r--r--haddock-library/fixtures/examples/list-blocks2.parsed10
1 files changed, 10 insertions, 0 deletions
diff --git a/haddock-library/fixtures/examples/list-blocks2.parsed b/haddock-library/fixtures/examples/list-blocks2.parsed
new file mode 100644
index 00000000..169677b7
--- /dev/null
+++ b/haddock-library/fixtures/examples/list-blocks2.parsed
@@ -0,0 +1,10 @@
+DocAppend
+ (DocAppend
+ (DocHeader
+ Header {headerLevel = 3, headerTitle = DocString "Title"})
+ (DocUnorderedList
+ [DocParagraph (DocString "List directly"),
+ DocAppend
+ (DocParagraph (DocString "after the title"))
+ (DocCodeBlock (DocString "with some inline things\n"))]))
+ (DocUnorderedList [DocParagraph (DocString "is parsed weirdly")])