Ensure all examples from the GFM specification pass in client-side Markdown parser
The problem
In %15.1, we finished implementing support for deserializing for all the content types specified in the Commonmark and the GitHub Flavored Markdown specifications in the Content Editor.
However, after running the Snapshot tests that @cwoolley-gitlab has been working on in !89953 (merged), we noticed that there are 48 examples from the GitHub Flavored Markdown specification that the Content Editor can’t deserialize in the client.
The solution
We should ensure that the client-side parser provides robust support for Commonmark and GFM before moving forward with implementing support for GitLab Flavored Markdown. This is important because we can’t deliver a client-side parser that can’t process Markdown that is already supported by the backend.
Availability and Testing
Please ensure content_editor_spec
E2E still passes for regression purposes. SET review of the MR would be beneficial.
Failing examples
-
118 !92384 (merged) -
122 !91706 (merged) -
123 !91706 (merged) -
124 !91706 (merged) -
125 !91706 (merged) -
129 !91706 (merged) -
131 !91706 (merged) -
133 !91706 (merged) -
137 !91628 (merged) -
138 !91706 (merged) -
139 !91706 (merged) -
140 !91706 (merged) -
141 !91706 (merged) -
142 !91706 (merged) -
143 !91706 (merged) -
144 !91706 (merged) -
145 !91706 (merged) -
146 !92376 (merged) -
147 !91706 (merged) -
148 !92376 (merged) -
149 !92376 (merged) -
150 !91706 (merged) -
151 !92376 (merged) -
152 !92376 (merged) -
153 !91706 (merged) -
154 !91706 (merged) -
155 !91706 (merged) -
157 !91706 (merged) -
158 !91706 (merged) -
170 !91706 (merged) -
288 !92376 (merged) -
289 !92376 (merged) -
500 !91706 (merged) -
525 !91628 (merged) -
532 !91706 (merged) -
539 !91628 (merged) -
544 !91706 (merged) -
632 !91706 (merged) -
633 !91706 (merged) -
634 !91706 (merged) -
636 !91706 (merged) -
653 !91706 (merged)