The latest updates on your projects. Learn more about Vercel for Git ↗︎

The code looks good but there are some simplifications we can apply before merge.

I think this is probably a net good change. It's small, isolated, has tests, and mostly prevents tables from being inserted in the UI without gutting the partial support for nested tables that exists elsewhere.

There are probably other situations where you could create tables programmatically, but rather than taking more extreme approaches (e.g. a transform) it probably makes sense to just chip away at nested table support. I think most of the work is handling DOM related issues with navigation (which probably shouldn't rely so much on DOM in this case).

Something that is probably going to come up is when a user pastes HTML with nested tables, the nested content is just going to disappear. We might want to accompany this change with some additional documentation somewhere that they should handle these cases in importDOM until nested tables are supposed.

Thanks for the detailed review @etrepum! I've updated the README to document the handling of nested tables, particularly focusing on the importDOM implementation as you suggested. The documentation now:

1. Clearly states that nested content will be removed by default during paste operations
2. Guides users on how to handle nested tables in their importDOM implementation
3. Provides high-level approaches for preserving nested table content

I haven't included specific code examples yet. Would you like me to add some practical examples of importDOM implementations to make it more concrete for users?

Let me know if you'd like any adjustments to the documentation or if there are other aspects we should cover.