EZP-30393: Moved all Online Editor front-end code to the RichText Bundle

[dew326]

Question	Answer
JIRA issue	EZP-30393
Requires:	ezsystems/ezplatform-page-builder#354 EZP-30393: Dropped Online Editor front-end code in favor of the RichText Bundle ezplatform-admin-ui#1014
Improvement	yes
New feature	no
Target version	master (2.0@dev) for eZ Platform v3.0
BC breaks	yes
Tests pass	yes
Doc needed	yes

Summary

This PR moves front-end code and back-end configuration related to AlloyEditor from AdminUI, keeping there minimal code just for embedding RichText.

Backward incompatible changes

• eZ.richText with proper keys replaced eZ.adminUiConfig.alloyEditor, eZ.adminUiConfig.richTextCustomTags, and eZ.adminUiConfig.richTextCustomStyles,
• All assets (js, scss, svg, fonts, etc.) have been moved from AdminUI bundle here, custom 3rd party development around OE needs to align with that.

New features

• Configuration for front-end is exposed as eZ.richText.
• Configuration can be also used in Twig templates using The ez_richtext_config Twig function.
• Configuration is now exposed via PHP API by means of auto-wirable \EzSystems\EzPlatformRichText\API\Configuration\ProviderService Symfony service.
• Auto-configurable Service Provider Interface \EzSystems\EzPlatformRichText\SPI\Configuration\Provider allows extending configuration by custom settings.

Documentation

eZ Platform RichText Bundle exposes Twig global variable ez_richtext_config which contains RichText and AlloyEditor configuration. In AdminUI this configuration is exposed for front-end as eZ.richText JavaScript variable and currently out-of-the-box provides the following configs: alloyEditor, customStyles, customTags. Please note that in any case AdminUI requires the RichText Bundle to be enabled.

The bundle also provides PHP API to retrieve that configuration. To use it, inject \EzSystems\EzPlatformRichText\API\Configuration\ProviderService (the service supports autowiring).

It is also possible to extend the configuration by implementing the SPI \EzSystems\EzPlatformRichText\SPI\Configuration\Provider. It's enough to register service implementing that interface and autoconfigure it.

TODO:

• Move custom attribute when it's merged (EZP-29301: Created UI for adding custom attributes on RichText elements ezplatform-admin-ui#996).
• Move AE list fix (EZP-30665: Custom styles dropdown becomes unusable when contains many… ezplatform-admin-ui#1015)
• Move configuration (backend)
  - Move eZ.adminUiConfig.alloyEditor to eZ.richText,
  - Move eZ.adminUiConfig.richTextCustomTags to eZ.richText.customTags,
  - Move eZ.adminUiConfig.richTextCustomStyles to eZ.richText.customStyles.

[alongosz]

Note: to be resolved later on.

[alongosz]

Addressed all CR issues, please review:

• 4dc9b6d
• 7458d31
• 31ecd7d
• bddd421
• 6acd3d1
• 00f9278
• 47a66d6
• d8cb3e0
• 99bf08e

[webhdx]

Good work, just a few comments from my side. What I find lacking is a description on what was added. I was not sure if I should write comments on the code which was most likely just moved and not even belong to you.

[alongosz]

Good work, just a few comments from my side. What I find lacking is a description on what was added. I was not sure if I should write comments on the code which was most likely just moved and not even belong to you.

@webhdx I've addressed all your comments. I value your input regardless of if this is a copied code or a new one. All the reviews for this PR prove that reviewing copied code is also useful.
That said, I've updated the description as well so it's more clear.