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
I would like to discuss this issue with anyone who is interested in cross-platform compatibility of Lexical data models, be it via JSON serialization (possible today) or via collaborative editing (coming in the future on iOS), hence posting an issue in the Lexical JS repository as well as in Lexical iOS.
The TLDR is, TextNode has a style field, which is arbitrary CSS information. Lexical iOS is not styled via CSS, and currently we don't handle this field. The question is what should we do -- attempt to convert the data, come up with a universal format, or just let the two platforms approach styling of text nodes separately and punt the problem on to the API consumer to handle syncing them up. Or maybe there's an approach I haven't thought of yet.
Comments and discussions welcome.
The text was updated successfully, but these errors were encountered:
Please see Issue 20 on facebook/lexical-ios for a description!
I would like to discuss this issue with anyone who is interested in cross-platform compatibility of Lexical data models, be it via JSON serialization (possible today) or via collaborative editing (coming in the future on iOS), hence posting an issue in the Lexical JS repository as well as in Lexical iOS.
The TLDR is, TextNode has a
style
field, which is arbitrary CSS information. Lexical iOS is not styled via CSS, and currently we don't handle this field. The question is what should we do -- attempt to convert the data, come up with a universal format, or just let the two platforms approach styling of text nodes separately and punt the problem on to the API consumer to handle syncing them up. Or maybe there's an approach I haven't thought of yet.Comments and discussions welcome.
The text was updated successfully, but these errors were encountered: