Challenges

[micgro42]

A list of (conceptual) problems that occurred and with which I'm not yet sure what to do. 🤔

• [ ] We want to have all information (group, name, spec, allowed subnodes, parsing, ...) about a Node in ideally in 1 place, preferably in php. However the spec requires a javascript function toDOM() and I see no nice way to write that in php.
• [ ] User may want to copy html from other wiki-pages and expect it to be correctly formatted in prosemirror. It may not be obvious how to do this for all syntax-elements (e.g. Interwikilinks #12 )
  • [ ] We need a way to test this "pasting stuff into the editor"-behaviour
• [x] links may be formatted as a whole, but not contain partial formatting ➡️ implement links as Node containing 0 or 1 TextNode with formatting

[splitbrain]

Remind me again why we would want to configure the Node in PHP? Would it be easier if we had one file per Node in JavaScript? IIRC we wanted PHP to reuse the parser mode configuration... Could we simply export that info to JavaScript and then reuse it in our Node classes?