Details
-
Story
-
Resolution: Done
-
High
-
None
-
[2.4] - Sprint 4
-
1
Description
Doing so will give us much more flexibility on evolutions of the feature:
- release fixes or major versions outside of the ezplatorm release cycle
- introduce BC breaks / major versions without having to bump ezpublish-kernel
- disable fieldtype entirely (whatever the reason)
The suggested name is ezsystems/ezplatform-richtext-fieldtype.
Backward compatibility
This should behave like ezplatform-http-cache, where compiler passes will disable the kernel services that are provided by this new package.