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
As a developer of the CLI and of custom plugins I don't want to care to much about edge cases in MD and HTML reports.
At the moment there are slight inconsistencies in the code that I have to know as CLI developer and as plugin developer I have to care about 3rd party information and treat edge cases like considering new lines after code blocks etc.
Acceptance criteria
The utils package should restructure the folders containing MD and HTML formats.
the 2 formats should live in the root of utils in folders called html and md
utils/
|-- src/
|-- lib/
|-- md/
|-- html/
remove constants like SPACE, TAB or NEW_LINE and place the characters directly
as some helpers are named the same (e.g. fontStyle) we should think about exporting the 2 formats in a way that does not cause duplicated exports
all produces content form helpers should be formatted readable
User story
As a developer of the CLI and of custom plugins I don't want to care to much about edge cases in MD and HTML reports.
At the moment there are slight inconsistencies in the code that I have to know as CLI developer and as plugin developer I have to care about 3rd party information and treat edge cases like considering new lines after code blocks etc.
Acceptance criteria
The
utils
package should restructure the folders containing MD and HTML formats.utils
in folders calledhtml
andmd
remove constants likeSPACE
,TAB
orNEW_LINE
and place the characters directlyfontStyle
) we should think about exporting the 2 formats in a way that does not cause duplicated exportsThe
utils
package should provide all needed MD elements as helper including good defaults:**{content}**
# H1\n
{content}\n{content}\n
{content}\n\n
{content}\n\n{content}\n\n
| Heading 1|......\n\n
models
The
utils
package should provide all needed MD elements as helper including good defaults:<b>{content}</b>
<table></table>\n\n
<details>\n<summary>{summary}<summary>\n{content}\n<details>
Implementation details
No response
The text was updated successfully, but these errors were encountered: