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
In Markdown, single line-breaks are ignored, in order to prevent editors for requiring wrapping (See Markdown specification).
This is especially significant when using it with things like JSDoc and other comments, as most codebases enforce strict line length limits in order to make code more readable and fit within smaller panes.
Current behavior
Presently, when vue-docgen-cli encounters a single line-break, it treats this as a true break and inserts a <br/> tag, instead of treating sets of lines as paragraphs, as most Markdown specifications dictate. The result is a bit icky.
To reproduce
The following:
defineProps<{/** * Msg prop. This prop is displayed in a Heading 1 tag with a green color, * in order to give it emphasis. Specifically, it's rendered using an * **<h1>** tag. * * Leaving this empty does not remove the **<h1>** from the DOM. * * Global <h1> styles will effect the way the `msg` prop appears. * * @see [Empty HTML Tags](/some/docs-link) * @see [H1 Tag - MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements) */msg: string;}>();
Produces:
Prop name
Description
Type
Values
Default
msg
Msg prop. This prop is displayed in a Heading 1 tag with a green color, in order to give it emphasis. Specifically, it's rendered using an <h1> tag.
Leaving this empty does not remove the <h1> from the DOM.
In Markdown, single line-breaks are ignored, in order to prevent editors for requiring wrapping (See Markdown specification).
This is especially significant when using it with things like JSDoc and other comments, as most codebases enforce strict line length limits in order to make code more readable and fit within smaller panes.
Current behavior
Presently, when
vue-docgen-cli
encounters a single line-break, it treats this as a true break and inserts a<br/>
tag, instead of treating sets of lines as paragraphs, as most Markdown specifications dictate. The result is a bit icky.To reproduce
The following:
Produces:
in order to give it emphasis. Specifically, it's rendered using an
<h1> tag.
Leaving this empty does not remove the <h1> from the DOM.
Global <h1> styles will effect the way the
msg
prop appears.@see
Empty HTML Tags@see
H1 Tag - MDNWhen sized down, this appears broken:
Expected behavior
@
should be considered paragraph breaksIn other words:
The following:
Should produce:
The following:
Should produce (to follow convention):
or
The following:
Should produce:
or
or even just
The text was updated successfully, but these errors were encountered: