Rich Text Editor should not destroy markdown

[schlichtanders]

Operating system

Linux

Joplin version

2.13.2

Desktop version info

Joplin 2.13.12 (prod, linux)

Client ID: c7dff86521c841b8b1f92fa6239cc51c
Sync Version: 3
Profile Version: 44
Keychain Supported: No

Revision: e027cdc

OCR: 0.3.2
Outline: 1.5.13
Typograms: 1.0.0

Current behaviour

1. install the typogram plugin
2. put the typogram example in a markdown note using Split Editor, save

```typogram
          +----+     o    |          o       *      *   .----------.
  *-+---. '-* -+-    |    v         ^         \    /    |.--------.|
    |   '--->   +----+  ->*<-      /   .-+->*<-o--+     |'------> ||
  <-'       *---+     |<----->|   +----' |  ^   \       '---------'|
                                         |__|    v      *----------'
```

3. switch to Rich Text Editor, make a change somewhere else and save
4. go back to Split Editor, you should already see the destroyed typogram example, save again
5. go back to Rich Text Editor and see that it finally got destroyed.

Expected behaviour

Even though the Rich Text Editor does not support all plugins smoothly, it should not destroy such information, shouldn't it?

Logs

No response

[laurent22]

This typogram contains valid Markdown elements so the RTE doesn't "destroy" it, it renders it. To prevent valid Markdown from being rendered, you need to wrap it in a code block (maybe that's something that the plugin needs to fix)

[schlichtanders]

@laurent22 Please reopen, I think the issue got misunderstood.

Of course I fenced the typogram - the confusion arose because here in github the fences are not shown. I now managed to show them - see above

[laurent22]

Would you mind sharing the whole note as a Markdown file so that we can see exactly how it looks?

[schlichtanders]

try this one:

my markdown file

```typogram
          +----+     o    |          o       *      *   .----------.
  *-+---. '-* -+-    |    v         ^         \    /    |.--------.|
    |   '--->   +----+  ->*<-      /   .-+->*<-o--+     |'------> ||
  <-'       *---+     |<----->|   +----' |  ^   \       '---------'|
                                         |__|    v      *----------'
```

[personalizedrefrigerator]

There is now an example available for how to make a renderer plugin work in the rich text editor:

joplin/packages/app-cli/tests/support/plugins/content_script/src/markdownItTestPlugin.ts

Lines 27 to 34 in a59ad20

	const richTextEditorMetadata = `
	<pre
	class="joplin-source"
	data-joplin-language="justtesting"
	data-joplin-source-open="\`\`\`justtesting\n"
	data-joplin-source-close="\`\`\`"
	>${markdownIt.utils.escapeHtml(token.content)}</pre>
	`;

joplin/packages/app-cli/tests/support/plugins/content_script/src/markdownItTestPlugin.ts

Lines 36 to 38 in a59ad20

	return `
	<div class="just-testing joplin-editable">
	${richTextEditorMetadata}

The data-joplin-language, data-joplin-source-open, data-joplin-source-close, class="joplin-editable", and <pre class="joplin-source" elements and attributes help Joplin reconstruct the original markdown that created the diagram.

Edit: See also #10178

[laurent22]

Since it's not something that we can fixed I reported it on the plugin repository: cwesson/joplin-plugin-typograms#1