1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
|
# Changelog for commonmark-extensions
## 0.2.5.5
* Fix auto_identifiers extension: it now replaces emojis with
their aliases, as documented.
* Fix auto_identifiers_ascii extension: it now ignores
non-ASCII characters with no ASCII equivalent.
## 0.2.5.4
* Fix autolink parsing regression (#151). This affects autolinks with
doubled internal line-ending punctuation characters.
## 0.2.5.3
* Fix rebase_relative_paths extension so it works with URLs with
non-ASCII characters (#148). Previously these would not be properly
detected as absolute URIs.
## 0.2.5.2
* Improve autolinks extension (#147).
The autolinks extension was interacting badly with explicit links,
To fix this we had to make autolink parsing a bit stricter than
the GFM spec does. They allow unbalanced `)` except at the end
of a URL (which is defined as: followed by optional final punctuation
then whitespace or eof). With this change, we don't allow unbalanced
`)` at all in raw URLs. This should not be a big problem in practice.
* Protect against quadratic generated table size explosion (Michael Howell).
This commit adds a limit to the number of auto-completed cells
around 200,000. The result is, in these original samples:
## 0.2.5.1
* Add `test/alerts.md` to extra-source-files in cabal file.
## 0.2.5
* Add support for alerts extension, supporting GitHub-style alerts (#132).
<https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts>
New module Commonmark.Extensions.Alerts [API change].
* Do not accept footnote labels with line breaks (Michael Howell).
* Parse `[^ ]` and `[^]` as links (Michael Howell). This is consistent with
most other CommonMark parsers, even when they have support for footnotes turned on.
## 0.2.4
* Make `pipe_tables` extension treat backslash escapes like GH does (#112,
Michael Howell). This change essentially changes the way the text
`\\|` gets parsed inside a table. In the old version, the first backslash
escapes the second backslash, and then the pipe is treated as a cell
separator. In the new version, the pipe is still preceded by a backslash,
so it is still literal text. The escaping rule is documented in detail
in the spec for this extension. This change also aligns our escaping
of pipes with GitHub's.
## 0.2.3.6
* Fix pipe table parser so that `|`s don't interfere with
other block structures (Michael Howell, #111, fixing #52 and
#95). This parser is structured as a system that parses the
*second* line first, then parses the first line. That is, if
it detects a delimiter row as the second line of a
paragraph, it converts the paragraph into a table. This
seems counterintuitive, but it works better than trying to
convert a table into a paragraph, since it might need to be
something else.
* Improve parsing of inline math (#110).
## 0.2.3.5
- Resolve entities inside wikilinks (#105, Michał Kukieła).
## 0.2.3.4
- Require whitespace after definition list marker (#104).
Otherwise we can inadvertently clobber strikeout or subscript.
## 0.2.3.3
- Fix definition_lists extension (#96). We were not properly consuming
indentation in definitions, which caused problems when the definitions
themselves contained lists.
## 0.2.3.2
- Update lower version bounds for commonmark (#93, David
Thrane Christiansen).
## 0.2.3.1
- `math` extension: don't fail when display math contains
embedded inline math. See jgm/pandoc#7942.
- Make math parsing more sophisticated.
Count embeddings inside `{..}`, since math can contain
e.g. `\text{...}` which itself contains math delimiters.
- Small improvement in pipe table parsing.
The old parser failed on some edge cases with extra whitespace
after pipes (which we should just ignore).
- `fancy_list` extension: improve list type ambiguity resolution (#89).
## 0.2.3
- Allow bare word attribute in fenced_divs (#84). This follows a similar
change in pandoc (jgm/pandoc#7242).
## 0.2.2.1
- Fix commonmark-extensions to build with GHC 9.2 (#81, Joseph C. Sible).
Currently `--allow-newer` is needed.
## 0.2.2
- Add footnote to gfmExtensions. Note that this also requires
additional type constraints on gfmExtensions [API change].
## 0.2.1.2
- Fix bug with absolute paths in rebase_relative_paths
extension on Windows.
## 0.2.1.1
- Fix bug in wikilinks extensions.
## 0.2.1
- Add `rebase_relative_paths` extension.
New exported module Commonmark.Extensions.RebaseRelativePaths [API change].
- Add `wikilinks_title_before_pipe` and `wikilinks_title_after_pipe`
extensions (#69).
New exported module Commonmark.Extensions.Wikilinks [API change].
## 0.2.0.4
- Add a test for autolinks (#66).
- Require commonmark 0.1.1.2 (otherwise autolinks don't work
properly).
## 0.2.0.3
- Add some new test examples to the autolinks extension spec (#65).
- Allow interior `~` characters in autolinks (#65).
## 0.2.0.2
- Remove unnecessary Typeable constraint on `TaskList` and
`gfmExtensions` (#58).
- Fix bug in `footnote` extension: multiple blocks in
a block container (e.g. block quote or list) inside
a footnote were being rendered in reverse order (#63,
Harald Gliebe).
## 0.2.0.1
- Added a missing test file to extra-source-files (#55).
## 0.2.0.0
- Add HasQuoted class in Smart extension, with singleQuoted
and doubleQuoted methods. This gives more fleibility in
supporting smart quotes, and allows us to use pandoc's
Quoted elements.
- Add advice to haddocks for pipeTableSpec (#52).
If a line could be a candidate pipe table heading, but the
following line of separators is not encountered, the line is
treated as a paragraph, even if it has indications of other
block-level formatting. Putting the pipeTableSpec AFTER
parsers for lists, headings, etc. causes the latter to take
priority.
## 0.1.0.0
- Initial release
|
