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

Enable option to use custom mjml parser instead of default one #341

Merged
merged 5 commits into from
Aug 21, 2024

Conversation

pavelstencl
Copy link

@pavelstencl pavelstencl commented Nov 16, 2023

Hi @artf ,

Thank you for your repository. It's fantastic! We've implemented our custom MJML-browser parser with additional components, but we're encountering issues using it in GrapesJS/mjml.

So I've included an option in the GrapesJS/mjml plugin config to override the default MJML parser. Would it be feasible to incorporate this feature into your package?

Thanks and cheers!

@RakulAgn
Copy link

@artf This is a good option to use. Why can't you merge and approve this? I am also looking forward to using custom MJML components."

@RakulAgn
Copy link

@pavelstencl Having Complete Demo is Great

Copy link
Member

@artf artf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @pavelstencl this is an awesome addition.
Sorry if it took some much time to finally merge it 😓

@artf artf merged commit 2924688 into GrapesJS:master Aug 21, 2024
1 check failed
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.

3 participants