Is there a reason TipTap deviated from Prosemirror in node naming? #5619
-
I'm working on porting over a DOM serializer to C# and have run into the annoying realisation that when exporting to JSON, TipTap uses camelCased naming convention for nodes and marks: I'm working alongside a C# port of Prosemirror so am trying to follow those conventions. It's definitely surmountable to deal with the difference, but more custom code to handle it and I was curious what the reasoning was for this change. Similarily, Tiptap uses I'm not looking for it to be changed (that's Breaking, and a major version bump), but to make sure there isn't a reason that will impact my code I should be aware of. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The naming of extensions was decided long ago. The names should not affect your application in anyway and you can override extension names |
Beta Was this translation helpful? Give feedback.
The naming of extensions was decided long ago. The names should not affect your application in anyway and you can override extension names