if the rule uses the node name to create a mark, it’d be weird to use it again in another rule to create a node
Ah, that’s a use case I didn’t account for: I was only thinking about parseRules in terms of model output and not html dom inputs.
Would an opt-in consuming: false flag on parse rules help you here?
Yes! This would allow me to use tags for mark pasteRules, and help with the text-underline scenario.