Acy Watson

We can add a more specific error message and/or some docs though - good call. Probably more like a feature, but sorry you lost time on this.

> Have you tried overriding `excludeFromCopy` in the Node itself? I believe that should work cc @acywatson Mmm, good thought, but this API is used mostly in copy/paste. The direct...

> Don't you think it's better to define the schema in a centralized place instead of having the schemas scattered across many files, which in turn can be rewritten with...

From Discord: > Perhaps our desire for schema normalization comes from limitations of older versions of Slate and the schema being the only way to salvage state that would otherwise...

@abelsj60 these aren't my words - just documenting some use cases set forth by someone on Discord. Generally, yea I guess there are contexts where you can direct Lexical to...

Just some research on Slates history with Schemas - they were completely replaced with [Normalization](https://docs.slatejs.org/concepts/11-normalizing) years ago: https://docs.slatejs.org/general/changelog#0.53-december-10-2019 The reasoning is because you can do anything with normalization (which is...

> First of all, I would like to highlight [the Prosemirror implementation](https://prosemirror.net/docs/guide/#schema), which I find more powerful, elegant and flexible than Slatejs. @EgonBolton Wow - just got done reading over...

> Here's another use-case. Say that we cut 3 paragraphs, then paste them inside a list item: > > ``` > insertion point > | > * > - TARGET...

> *With methods I mean things like insertAfter, insertBefore, canBeEmpty, isShadowRoot, etc. They are in fact a way of normalizing. Sort of - these aren't all the same. The first...

Here are the broad categories use cases I see so far: 1) **Inserting content** into the editor at an arbitrary location. You can construct a tree that isn't valid to...