-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuemark2.0 issues #379
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
*** Bold Italic ***
& HR
This comment was marked as resolved.
This comment was marked as resolved.
Thank youu! |
The first half (before PS: I started building a test using the |
This comment was marked as resolved.
This comment was marked as resolved.
No more loops with unclosed image tags such as |
Are image reflinks like |
btw: Nuemark will not support raw HTML, because that violates the separation of concerns principle |
The commonmark reference implementation does support it: https://spec.commonmark.org/dingus/?text=!%5Bimg%5D%5Btag%5D%0A%0A%5Btag%5D%3A%20%2Fimg.png%0A#result (PS: did you do the strike through implementation with one tilde ( Edit : you can btw remove |
Found more problems: 1. **bold** not bold **bold**
2. **test**: expected: <ol>
<li><p><strong>bold</strong> not bold <strong>bold</strong></p></li>
<li><p><strong>test</strong>:</p></li>
</ol> reality: <ol>
<li><p><strong>bold** not bold **bold</strong></p></li>
<li><p>**test**:</p></li>
</ol> You can see this issue e.g. on the Edit: maybe the |
Nuemark also doesn't support foo
bar
foo\
bar expected: <p>foo<br />
bar</p>
<p>foo<br />
bar</p> |
Doing a quick code review of your dev branch, I am confused if the Blocks or Inline is scanned first? If Blocks, then it seems this code:
Would render as an
<hr>
since you are just scanning first few characters.?Also be aware that CommonMark is VERY flexible for
<hr>
. I personally don't think you need to cover every edge case, but it could help to document "Only the common Markdown/CommonMark rules are covered."The text was updated successfully, but these errors were encountered: