Repository navigation
Replies: 2 comments 1 reply
|
This ultimately follows the same rules as for a ProseMirror View native custom node view. When using a custom node view, parseDOM and toDOM are only used for clipboard interactions, so you just need to choose a DOM serialization that contains all of the data you would need in order to re-hydrate a pasted chunk of HTML into the same node. (If that wasn't a helpful description, let me know and I can write up some examples). It looks like this isn't really documented in the ProseMirror reference docs, either. I'm not opposed to adding some docs here that explain this. Maybe just an FAQ section that includes a question like "Do I still need |
1 reply
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.
I have a working editor, but it's kind of by dumb luck.
There's no documentation for what the ProseMirror schema should look like for Nodes and Marks that use a React component as their view. Specifically, I'm not clear on what needs to be provided in the
parseDOMandtoDOMmethods?Happy to help write docs and examples for this, but I need to understand it better before I'd be able to contribute.
All reactions