Daniel Steigerwald

That's what I wrote "here can NOT be encrypted text"

> encrypt it when you save it I wrote we can't encrypt it without sacrificing incremental syncing because I was curious whether I am not missed something. > incremental synchronization...

I had the same problem with the Image component (unreproducible) and now I have the same problem with Pressable and keypress. The mouse click is OK, keyboard enter press not.

Ignore it. It's past https://github.com/facebook/react/pull/22114

Maybe I am overlooking something, but "If a document is just a flat sequence, hitting enter in the middle of a paragraph just means inserting a '\n' element into that...

I wish TypeScript "port" exists (tongue in cheek).

All we need for the React Native are constants and common vocabulary for https://github.com/este/este/blob/master/src/common/app/theme.js Then the helper for fonts.

> Is your thought that this would just auto-create a bunch of components wrapping... Not at all. https://twitter.com/estejs/status/757338696735653889 and https://twitter.com/estejs/status/757709752004710400

Yeah, something like that. Will investigate soon. Thank you.

Yes, we should start with the minimal subset, for example, only headings, paragraph, lists, image, form fields, etc. I would say people will like to add own custom UI elements...