[lexical-table] Return inserted node from $insertTableRow__EXPERIMENTAL and $insertTableColumn__EXPERIMENTAL

[amanharwara]

Description

Currently, the $insertTableRow__EXPERIMENTAL function doesn't return anything, so if you want to insert a table row using it and do something with the inserted row, you'll have to do all the calculations again to find the inserted row.
With this PR, the function will return the inserted row node if it was successful and undefined if not. This removes the need for rewriting all the logic regarding spans just to find the inserted row.
Also returns the first inserted cell from $insertTableColumn__EXPERIMENTAL

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
lexical	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 16, 2024 2:37pm
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 16, 2024 2:37pm

[github-actions]

size-limit report 📦

Path	Size
lexical - cjs	29.94 KB (0%)
lexical - esm	29.78 KB (0%)
@lexical/rich-text - cjs	38.51 KB (0%)
@lexical/rich-text - esm	31.58 KB (0%)
@lexical/plain-text - cjs	37.16 KB (0%)
@lexical/plain-text - esm	29 KB (0%)
@lexical/react - cjs	40.29 KB (0%)
@lexical/react - esm	33 KB (0%)

[ivailop7]

Would this actually work the way you intend to use it though? When you insert the row, the updated state needs to be commited, before using it, so you would need to do another editor.update(), at which point you could now get the just appended node key, etc after the committed state. Maybe @etrepum could confirm if I'm right or wrong here.

[etrepum]

I think it would be perfectly reasonable to do something with the result, e.g. populate some default content into the cells. The update commit concern is only relevant if you're trying to do something with the DOM after it's rendered.