[wip] feat: add "Copy as document" to copy rich markdown into emails and documents #2367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I will often write something in Logseq that I want to send via email or make part of a Google Doc / Dropbox Paper. "Copy as TEXT" has two problems:
_foo_
instead of foo) and then I need to transform it manuallyI added "Copy as DOCUMENT" that changes both of those things. IMO, this should be the behavior of "Copy as TEXT" but maybe others use it differently and have other expectations.
Note that Copy as Document only gives you rich text when you paste into an editor that can handle it. Otherwise, it gives you the same format as Copy as TEXT but with the children contents
TODO in this PR