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

allow parseOptions to be passed to setContent and Editor constructor #254

Merged
merged 1 commit into from
Apr 11, 2019
Merged

Conversation

mayacoda
Copy link
Contributor

@mayacoda mayacoda commented Apr 8, 2019

As requested in #168, I added the possibility to pass parserOptions to both the Editor constructor and when calling .setContent(). Passing to the constructor was necessary for loading content that contains whitespaces which need to be preserved.

@philippkuehn philippkuehn merged commit 7a17b56 into ueberdosis:master Apr 11, 2019
@philippkuehn
Copy link
Contributor

Thanks, Maya!

@mayacoda
Copy link
Contributor Author

Thanks for the speedy merge! Do you know when this will be published on npm?

@philippkuehn
Copy link
Contributor

It's published now!

thomtrp added a commit to twentyhq/twenty that referenced this pull request Oct 28, 2024
Tiptap uses non breaking spaces between nodes (like variables). Those
html characters are not properly handles in emails. Replacing by regular
spaces during parsing.

I tried to fix it in settings but looks like this is only for preserving
those nbsp and not for removal (see
ueberdosis/tiptap#254)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants