wrong generation of richtext (lexical) field typescript type #15022
artimalternar
started this conversation in
Feature Requests & Ideas
Replies: 1 comment
-
|
This was necessary to make the generated types compatible with our In the future we'll update the generated types to be strongly typed - so all available node types are automatically typed. This should hopefully restore compatibility with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
before version 3.66.0 payload generated richtext ( lexical ) field as following
where
children->typewas of typestringbut after v3.66.0 it generates
children->typeas of typeanybut
lexicalv0.35.0 still requireschildren->typeas of typestringso we have a type mismatch as our frontend uses exact
SerializedEditorStatefromlexicallibraryBeta Was this translation helpful? Give feedback.
All reactions