Skip to content
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

fix(richtext-lexical): formatted inline code resulted in incorrect markdown export #10413

Merged
merged 2 commits into from
Jan 7, 2025

Conversation

AlessioGr
Copy link
Member

@AlessioGr AlessioGr commented Jan 7, 2025

If the following markdown:

**`text`**

was imported and then re-exported, the result was

`**text**`

Which would have been rendered as

<code>**text**</code>

Instead of

<strong><code>text</code></strong>

@AlessioGr AlessioGr enabled auto-merge (squash) January 7, 2025 05:52
@AlessioGr AlessioGr disabled auto-merge January 7, 2025 05:56
@AlessioGr AlessioGr enabled auto-merge (squash) January 7, 2025 05:58
@AlessioGr AlessioGr merged commit 827c75a into main Jan 7, 2025
68 checks passed
@AlessioGr AlessioGr deleted the fix/lexical-formatted-inline-code branch January 7, 2025 06:13
Copy link
Contributor

github-actions bot commented Jan 7, 2025

🚀 This is included in version v3.15.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant