You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lexical-collab will only reliably sync enumerable properties of nodes. This means that nodes participating in collab that are using properties instead of NodeState should initialize all of their properties in the constructor, even if to undefined.
We should probably also do a sweep over the existing nodes to make sure they all have explicit initializers (maybe write a lint to check for optional properties in node subclasses and disallow that syntax, foo: undefined | string will require explicit constructor initialization when foo?: string does not)
lexical-collab will only reliably sync enumerable properties of nodes. This means that nodes participating in collab that are using properties instead of NodeState should initialize all of their properties in the constructor, even if to
undefined
.We should probably also do a sweep over the existing nodes to make sure they all have explicit initializers (maybe write a lint to check for optional properties in node subclasses and disallow that syntax,
foo: undefined | string
will require explicit constructor initialization whenfoo?: string
does not)See also #7276, #7277
The text was updated successfully, but these errors were encountered: