Bug: In an editable EditorState after Parsed, typing will create a new TextNode instead of continuing with the last TextNode

Lexical version: 0.3.6

Steps To Reproduce

With TextNode

1. Refresh browser in code sandbox link
2. Editor should AutoFocus
3. type anything, see in TreeView that a new TextNode was created

With AutoLinkNode

1. Uncomment SerializedAutoLinkNode json in state
2. Refresh browser in code sandbox link
3. Editor should AutoFocus
4. type m to complete the link, see in TreeView that a new TextNode with m was created, and AutoLinkNode was destructed

Link to code example:

https://codesandbox.io/s/lexical-plain-text-example-forked-t3cgjf?file=/src/Editor.js

The current behavior

• On fresh parsing, editor won’t consider the last TextNode, will blindly create a new TextNode and won’t merge it with its predecessor

The expected behavior

• The last TextNode should be open for edit, new input should be considered part of that TextNode
• AutoLinkNode shouldn’t collapse, it should take new input as part of its child TextNode

[fantactuka]

Yeah, I guess once state is serialized you can recursively run through the tree to cleanup unused fields, and once it loaded for to be passed into editor do same, but to populate default values. I want to hear more from other folks whether they can think of any downsides of supporting missed fields and using default values before doing this change

[ProvidenceXz]

That’s exactly what I’ve been doing. Look forward to the resolution 😃