The tests at the end of MarkdownFormatterTest seem to be commented out by private? Not sure why, but the tests work even after commenting it out to #private. The patch is included including a unit test. ![]() Double spaces or trailing spaces should get turned into single spaces as well. So I would strongly vote to change the default behavior towards more standard Markdown / GFM to stay compatible with the world. rigmaroleAugust 12, 2020, 6:23pm 2 Every Markdown implementation I’ve tried removes white space in this same way. I guess we are not that rare when we intend to share Markdown sources between Redmine and GitLab and among Redmine and other systems - using API, mirroring wiki to git and indeed with users' copy&pasting it. And as the author says, it is against Markdown specs. On the other hand, it breaks compatibility with GFM, especially on its two major implementations GitHub and GitLab (as said - except GitHub issues, but our developers are really angry about GitHub issues having different behaviour than the rest of GitHub). Indeed, we do not know how intentional the decision was. This works as intended and inserts the tags in the. I see value in applying the linter to the README. ![]() ![]() On one hand, calling this a defect might not be fair, as it is apparently kind-of decision made in lib/redmine/wiki_formatting/markdown/formatter.rb with the setting :hard_wrap => true. I am then outputting this into a markdown e-mail but also converting any line-breaks using nl2br(). After applying a line length limit of 80 characters on the pre-commit check of markdown-lint, I was experiencing some difficulties in including a markdown table that I create with more width than 80 characters.
0 Comments
Leave a Reply. |