Editor improvements #486

병합
elegaanz editor-improvements 에서 master 로 14 commits 를 머지했습니다 5 년 전
elegaanz 코멘트됨, 5 년 전 (Migrated from github.com)
  • 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
- 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: - [x] make it possible to escape draft mode - [x] display errors from the server - [x] button to go back to the "normal" editor - [x] Avoid publishing placeholders
trinity-1686a 코멘트됨, 5 년 전
소유자
If I may add to the todo list: https://github.com/Plume-org/Plume/pull/458#issuecomment-473323102
codecov[bot] 코멘트됨, 5 년 전 (Migrated from github.com)

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
# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/486?src=pr&el=h1) Report > Merging [#486](https://codecov.io/gh/Plume-org/Plume/pull/486?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/c7ee779f51729326567a4c4bdeb416d8882f4b0a?src=pr&el=desc) will **decrease** coverage by `2.26%`. > The diff coverage is `n/a`. ```diff @@ 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 코멘트됨, 5 년 전 (Migrated from github.com)

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

@fdb-hiroshima Yes, the first one is already fixed, I'll see for the other. :)
trinity-1686a 검토됨 5 년 전
trinity-1686a 코멘트됨, 5 년 전
소유자

I think basic-editor should be permanent, and there would then be a button to re-enable the "advanced" editor

I think basic-editor should be permanent, and there would then be a button to re-enable the "advanced" editor
elegaanz (Migrated from github.com) 검토됨 5 년 전
elegaanz (Migrated from github.com) 코멘트됨, 5 년 전

I don't really know how to name it…

I don't really know how to name it…
trinity-1686a 검토됨 5 년 전
trinity-1686a 코멘트됨, 5 년 전
소유자

rich text editor?

rich text editor?
trinity-1686a 검토됨 5 년 전
trinity-1686a left a comment
소유자

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)

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 코멘트됨, 5 년 전 (Migrated from github.com)

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

@fdb-hiroshima This should definitely be fixed before merging this branch I think. I will see what I can do.
trinity-1686a 코멘트됨, 5 년 전
소유자

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

The only fix I see is, given the following : ```html <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 `div`s
elegaanz 코멘트됨, 5 년 전 (Migrated from github.com)

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
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 (Migrated from github.com) 검토됨 5 년 전
igalic (Migrated from github.com) left a comment

please remove the callgrind output files from the PR

please remove the callgrind output files from the PR
trinity-1686a 이 변경사항을 승인하였습니다. 5 년 전

리뷰어

trinity-1686a 이 변경사항을 승인하였습니다. 5 년 전
The pull request has been merged as 1f7ff62c19.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b editor-improvements master
git pull origin editor-improvements

Step 2:

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff editor-improvements
git push origin master
로그인하여 이 대화에 참여
No reviewers
마일스톤 없음
담당자 없음
참여자 2명
알림
마감일
기한이 올바르지 않거나 범위를 벗어났습니다. 'yyyy-mm-dd'형식을 사용해주십시오.

마감일이 설정되지 않았습니다.

의존성

No dependencies set.

Reference: Plume/Plume#486
불러오는 중...
아직 콘텐츠가 없습니다.