You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2021. It is now read-only.
Thank you for the detailed experiment. 2 questions:
What are the biggest pitfalls to pursue integrating react components in grapesjs - in the sense of further development?
What comes into your mind if webcomponnets would be instead of react components?
Kind Regards
The text was updated successfully, but these errors were encountered:
Well, I have not really worked with grapsejs since I created this POC implementation, so I don't really know what problems one may face when using react components + grapsejs together in the wild. But I will come back to this some day and will investigate more, because I will eventually need this in one of my projects.
However my solution seems a bit bloated with my own HTML parser implementation compared to @emilsedgh's solution, which is more elegant, although this codesandbox unfortunately doesn't work anymore:
Hey guys. I don't know why the code sandbox is broken. Unfortunately I don't have the time to look into that right now.
I think, and I hope, within the next year I'll have the chance to get back to this project and come up with a properly maintained and released version.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear @beepsoft ,
Thank you for the detailed experiment. 2 questions:
What are the biggest pitfalls to pursue integrating react components in grapesjs - in the sense of further development?
What comes into your mind if webcomponnets would be instead of react components?
Kind Regards
The text was updated successfully, but these errors were encountered: