Minimize handling of changes made into AztecText

[wordpress-mobile]

Minimize handling of changes made into AztecText

[koke]

From my limited knowledge, I think the right approach to this is to leverage shouldComponentUpdate to decide when we need to re-render.

I see some of that logic already in withSelect and @wordpress/element so we might even get that for free in the future, but I'm still a bit lost on that part.

[diegoreymendez]

The update issue is not specific to RN though, although I can imagine it'd be more apparent. I can't remember right now if we made improvements for this in WPiOS, but we had already spotted the need to avoid updating the post state and saving on each keystroke.

That said, I'm not too sure if the one to define the logic for saving should be the editor or the consuming app.

[SergioEstevao]

@mchowning this looks related to: #1941

[hypest]

Another aspect to add is: who owns the undo history and what "chunks" of change are saved as a single undo record?

Currently, Aztec owns its editing history, including of course raw text modifications (versus, for example, styling changes). I think we will probably need to implement something clever there to efficiently store content changes in the RN/app state.

In that sense, I can't tell yet exactly when the Aztec instance should re-render or how often. I think I'd like to see some implementation of the undo/redo logic before forming an opinion.

[hypest]

The Aztec integration has changed quite a bit for some time now (with RichText component on the Gutenberg-web side) and this ticket is now hard to relate to any particular code part. The ticket was originally raised for visibility purposes so, closing now as out-of-date.