-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[FR] Make Markdown support more robust #146
Labels
Comments
zoli
pushed a commit
to LucasXu0/AppFlowy
that referenced
this issue
Aug 30, 2023
fix: problem with the position of the floating operation bar
839900146
pushed a commit
to 839900146/AppFlowy
that referenced
this issue
Jun 6, 2024
* chore: update ws frame size * chore: update * chore: update frame size to 64 kb * chore: fix merge * chore: update * chore: update collab rev * chore: update * chore: update * chore: update * chore: update * chore: update * chore: update ws state * chore: update pg max connect * chore: fix crash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1~3 main use cases of the proposed feature
I want to be able to export more elaborate structure to Markdown
I want to be sure that Markdown export will function and have sensible defaults when it doesn't recognize a tag
what types of users can benefit from using your proposed feature
Any user who wishes to export a Document to Markdown
Additional context
We have an internal structure called Delta, we must ensure that every tag in Delta can be exported to Markdown. Markdown itself does not support all of the features that Delta does, but this can be handled with HTML tags. However, it is (apparently) not recommended to use HTML tags. So we shouldn't just go adding them willy-nilly.
The text was updated successfully, but these errors were encountered: