Replies: 1 comment
-
|
You'd have to implement your own serialization or use some compression, there's a lot of redundant information in the current JSON representation for lexical nodes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
I’m having an issue with the Table plugin. When a table is added to the editor, the generated editor state becomes extremely large. Because of this, saving the full JSON state to my database results in an oversized payload that exceeds my API payload limits. I’m looking for guidance on how to reduce the table node size, serialize it more efficiently, or apply a more optimized storage approach. Any suggestions or best practices would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions