Editor improvements

[elegaanz]

• Make it possible to insert new paragraphs in the article body
• Make it impossible to copy formatted HTML (to make media insertion from markdown code work correctly)

TODO:

• make it possible to escape draft mode
• display errors from the server
• button to go back to the "normal" editor
• Avoid publishing placeholders

[trinity-1686a]

If I may add to the todo list: #458 (comment)

[codecov]

Codecov Report

Merging #486 into master will decrease coverage by 2.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #486      +/-   ##
==========================================
- Coverage   26.83%   24.56%   -2.27%     
==========================================
  Files          65       65              
  Lines        9000     7116    -1884     
==========================================
- Hits         2415     1748     -667     
+ Misses       6585     5368    -1217

[elegaanz]

@fdb-hiroshima Yes, the first one is already fixed, I'll see for the other. :)

[trinity-1686a]

It's a bit sad markdown does not work with the rich editor (cmark see some div so it assumes it's only html and does not attempt to parse markdown)

[elegaanz]

@fdb-hiroshima This should definitely be fixed before merging this branch I think. I will see what I can do.

[trinity-1686a]

The only fix I see is, given the following :

<div>some text</div><div>![desc](path/to/picture.png)</div>

Where we are given a single Html("<div>some text</div><div>![desc](path/to/picture.png)</div>"), we could cut it out as ["some text", "![desc](path/to/picture.png)"], call cmark on each of these, and put back the divs

[elegaanz]

I was more thinking of pre-processing the HTML with the DOM APIs in WASM, because your solution may break footnotes, or links that use this syntax:

my [link]

[link]: https://example.org

[igalic]

please remove the callgrind output files from the PR

Callgrind files have been removed