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

Documentation for customMarkdownRenderer #1923

Closed
Powersource opened this issue Oct 20, 2021 · 5 comments
Closed

Documentation for customMarkdownRenderer #1923

Powersource opened this issue Oct 20, 2021 · 5 comments

Comments

@Powersource
Copy link

I'm trying to fix my issue mentioned here #485 (comment) so I'm looking into how to use the customMarkdownRenderer but I can't find any clear documentation on how to use it. There is some stuff in #1343 that I'll read now but would be nice to have it somewhere easier to find and more elaborated

@Powersource
Copy link
Author

Solved this for now by filtering away BR tags with a regex in the onChange handler instead cobudget/cobudget@f184ee9

@js87zz
Copy link
Contributor

js87zz commented Oct 25, 2021

@Powersource
Sorry for late replying.

I think we need to modify our internal code for the customization of a paragraph.
First of all, what I want to know for sure is that you want to handle \n as the softbreak?

Our editor handles \n as a hardbreak for compatibility with WYSIWYG.

It'll be helpful if you tell me exactly what kind of operation you want for converting.

@Powersource
Copy link
Author

Powersource commented Oct 25, 2021

I don't know exactly what it means to handle it as a softbreak. All I want really is that the markdown output from the editor should be able to be rendered correctly with https://github.com/remarkjs/remark-gfm Which in this case means removing the <br> and replacing it with something else. Replacing it with \n\n seems to give me output I'm happy with. edit: although I guess \n isn't markdown either, but I hope you get what i mean

@stale
Copy link

stale bot commented Nov 25, 2021

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

@stale stale bot added the inactive label Nov 25, 2021
@stale
Copy link

stale bot commented Jan 8, 2022

This issue will be closed due to inactivity. Thanks for your contribution!

@stale stale bot closed this as completed Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants