You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc.
Is this a feature or a bug?
Feature
Bug
π€·ββοΈ
Please describe the actual behavior.
My problem arose when I wanted to make a list of items in TSDoc. Eventually, I found that the formatting capabilities are not very consistent. Let's consider the following example
This means that everything which is not separated by an empty line, gets inlined. That seems pretty straight forward. However it breaks the list created with dashes, i.e. - md list item . As mentioned in #1441 and microsoft/tsdoc#178
So here I thought: ok, let's use html for everything. The TSDoc in not going to look great but the result might be worth it. When running the api-documenter to generate markdown, we get
π€ All of the markdown , except the inlined list items, got escaped. HTML mostly stayed, but <h2> tags and similar got escaped as well.
Are there any decisions behind this? Maybe mentioning the behaviour in the documentation could help somebody...
Or is this something nobody has faced before?
Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc.
Is this a feature or a bug?
π€·ββοΈ
Please describe the actual behavior.
My problem arose when I wanted to make a list of items in TSDoc. Eventually, I found that the formatting capabilities are not very consistent. Let's consider the following example
the content of doc model looks like
This means that everything which is not separated by an empty line, gets inlined. That seems pretty straight forward. However it breaks the list created with dashes, i.e.
- md list item
. As mentioned in #1441 and microsoft/tsdoc#178So here I thought: ok, let's use html for everything. The TSDoc in not going to look great but the result might be worth it. When running the api-documenter to generate markdown, we get
π€ All of the markdown , except the inlined list items, got escaped. HTML mostly stayed, but
<h2>
tags and similar got escaped as well.Are there any decisions behind this? Maybe mentioning the behaviour in the documentation could help somebody...
Or is this something nobody has faced before?
FYI, using
The text was updated successfully, but these errors were encountered: