Bug: Invalid nodes nesting

There’s an issue with copy-pasting when heading can end up nested into paragraphs. Same applies to all other sorts of invalid nesting (code block inside paragraph or list item, etc). Although we have several places assuming paragraph, heading, quote, code and list are either root-level children or nested into table cell, it’s not enforced in any way and you can replicate wrong nesting either by copy-pasting such content or by creating it via nodes api:

// Clipboard
<p><h1>Heading within paragraph</h1></p>
<ul>
  <li><h1>Heading within list</h1></li>
</ul>

...

// Api
$createParagraphNode().append(
  $createHeadingNode('h1').append(
    $createTextNode('Heading within paragraph')
  )
);

[acywatson]

Regarding the sanitization, what about a normalization API like slate’s? I’ve been looking for something like this myself, and it seems like it would benefit the core too.

About the problem of limiting functionality when putting this in the core, I guess it ties to the overarching question of how to make it more extendable and customizable. If there was a good system for that in place (I don’t know how that would look like), it wouldn’t be a big issue, and lexical could have sane defaults while still allowing for users to override and extend those defaults at will.

This is really interesting - especially this part:

https://docs.slatejs.org/concepts/11-normalizing#built-in-constraints

We actually share the majority of these constraints and it would be great to document them. I like the idea of generally being able to declare constraints or invariants and remediations for them through some API like this.

[thegreatercurve]

This should be fixed with schemas.