Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-28009

Extract the RichText FieldType to its own package

    Details

    • Sprint:
      [2.4] - Sprint 4
    • Story Points:
      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.

        Issue Links

          Activity

          Bertrand Dunogier created issue -
          Bertrand Dunogier made changes -
          Field Original Value New Value
          Labels candidate-for-next-sprint
          Bertrand Dunogier made changes -
          Status Backlog [ 10000 ] Specification [ 10002 ]
          Bertrand Dunogier made changes -
          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`.

          h3. About other FieldTypes
          This structure is already used for the Landing Page Field Type.
          While it may make sense for other Core Field Types, it is much more valuable for RichText, as its complexity is way larger than all other core Field Types together:

          {code}
          29434 RichText
          1989 Image
          1885 Page
          1636 BinaryBase
          1169 Keyword
          1048 Url
          1007 MapLocation
          918 User
          689 Media
          510 Country
          503 DateAndTime
          479 ISBN
          478 RelationList
          466 Relation
          464 Selection
          445 Time
          439 Author
          421 Date
          410 Integer
          408 BinaryFile
          398 Float
          383 TextLine
          338 CustomScalar
          338 EmailAddress
          327 TextBlock
          269 Checkbox
          192 Rating
          190 Null
          86 Price
          {code}

          FieldTypes with externale storage will come second, but are still way smaller (note that Image has code in other parts of the system, in regards to variations).
          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`.

          h3. About other FieldTypes
          This structure is already used for the Landing Page Field Type.
          While it may make sense for other Core Field Types, it is much more valuable for RichText, as its complexity is way larger than all other core Field Types together:

          {code}
          29434 RichText
          1989 Image
          1885 Page
          1636 BinaryBase
          1169 Keyword
          1048 Url
          1007 MapLocation
          918 User
          689 Media
          510 Country
          503 DateAndTime
          479 ISBN
          478 RelationList
          466 Relation
          464 Selection
          445 Time
          439 Author
          421 Date
          410 Integer
          408 BinaryFile
          398 Float
          383 TextLine
          338 CustomScalar
          338 EmailAddress
          327 TextBlock
          269 Checkbox
          192 Rating
          190 Null
          86 Price
          {code}

          FieldTypes with externale storage will come second, but are still way smaller (note that Image has code in other parts of the system, in regards to variations).

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          - how we handle BC
          Bertrand Dunogier made changes -
          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`.

          h3. About other FieldTypes
          This structure is already used for the Landing Page Field Type.
          While it may make sense for other Core Field Types, it is much more valuable for RichText, as its complexity is way larger than all other core Field Types together:

          {code}
          29434 RichText
          1989 Image
          1885 Page
          1636 BinaryBase
          1169 Keyword
          1048 Url
          1007 MapLocation
          918 User
          689 Media
          510 Country
          503 DateAndTime
          479 ISBN
          478 RelationList
          466 Relation
          464 Selection
          445 Time
          439 Author
          421 Date
          410 Integer
          408 BinaryFile
          398 Float
          383 TextLine
          338 CustomScalar
          338 EmailAddress
          327 TextBlock
          269 Checkbox
          192 Rating
          190 Null
          86 Price
          {code}

          FieldTypes with externale storage will come second, but are still way smaller (note that Image has code in other parts of the system, in regards to variations).

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          - how we handle BC
          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}}.

          h3. About other FieldTypes
          This structure is already used for the Landing Page Field Type.
          While it may make sense for other Core Field Types, it is much more valuable for RichText, as its complexity is way larger than all other core Field Types together:

          {code}
          29434 RichText
          1989 Image
          1885 Page
          1636 BinaryBase
          1169 Keyword
          1048 Url
          1007 MapLocation
          918 User
          689 Media
          510 Country
          503 DateAndTime
          479 ISBN
          478 RelationList
          466 Relation
          464 Selection
          445 Time
          439 Author
          421 Date
          410 Integer
          408 BinaryFile
          398 Float
          383 TextLine
          338 CustomScalar
          338 EmailAddress
          327 TextBlock
          269 Checkbox
          192 Rating
          190 Null
          86 Price
          {code}

          FieldTypes with externale storage will come second, but are still way smaller (note that Image has code in other parts of the system, in regards to variations).

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          - how we handle BC
          Bertrand Dunogier made changes -
          Status Specification [ 10002 ] Specification Review [ 10038 ]
          Bertrand Dunogier made changes -
          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}}.

          h3. About other FieldTypes
          This structure is already used for the Landing Page Field Type.
          While it may make sense for other Core Field Types, it is much more valuable for RichText, as its complexity is way larger than all other core Field Types together:

          {code}
          29434 RichText
          1989 Image
          1885 Page
          1636 BinaryBase
          1169 Keyword
          1048 Url
          1007 MapLocation
          918 User
          689 Media
          510 Country
          503 DateAndTime
          479 ISBN
          478 RelationList
          466 Relation
          464 Selection
          445 Time
          439 Author
          421 Date
          410 Integer
          408 BinaryFile
          398 Float
          383 TextLine
          338 CustomScalar
          338 EmailAddress
          327 TextBlock
          269 Checkbox
          192 Rating
          190 Null
          86 Price
          {code}

          FieldTypes with externale storage will come second, but are still way smaller (note that Image has code in other parts of the system, in regards to variations).

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          - how we handle BC
          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}}.

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          - how we handle BC
          Bertrand Dunogier made changes -
          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}}.

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          - how we handle BC
          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}}.

          h3. Backward compatibility
          This should behave like ezplatform-http-cache, where compiler passes will disable the kernel services that are provided by this new package.

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          Bertrand Dunogier made changes -
          Link This issue blocks EZP-28834 [ EZP-28834 ]
          Roland Benedetti made changes -
          Status Specification Review [ 10038 ] Specification Done [ 10003 ]
          Bertrand Dunogier made changes -
          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}}.

          h3. Backward compatibility
          This should behave like ezplatform-http-cache, where compiler passes will disable the kernel services that are provided by this new package.

          h3. Missing items from the spec
          - list affected items (config, core, ... ?)
          - determine the namespace to use
          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}}.

          h3. Backward compatibility
          This should behave like ezplatform-http-cache, where compiler passes will disable the kernel services that are provided by this new package.
          Roland Benedetti made changes -
          Sprint [2.1] Sprint 3 [ 97 ]
          Roland Benedetti made changes -
          Rank Ranked lower
          Roland Benedetti made changes -
          Story Points 5
          Andrzej Longosz made changes -
          Component/s Field types [ 10302 ]
          Andrzej Longosz made changes -
          Component/s Platform > Repository & Services (Public API impl) [ 10309 ]
          Andrzej Longosz made changes -
          Status Specification Done [ 10003 ] Development [ 3 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ] Andrzej Longosz [ andrzej.longosz@ez.no ]
          Roland Benedetti made changes -
          Story Points 5 3
          Roland Benedetti made changes -
          Sprint [2.1] Sprint 3 [ 97 ] [2.1] Sprint 4 [ 98 ]
          Bertrand Dunogier made changes -
          Sprint [2.1] Sprint 4 [ 98 ]
          Bertrand Dunogier made changes -
          Status Development [ 3 ] Specification Done [ 10003 ]
          Assignee Andrzej Longosz [ andrzej.longosz@ez.no ]
          Bertrand Dunogier made changes -
          Status Specification Done [ 10003 ] Specification Review [ 10038 ]
          Bertrand Dunogier made changes -
          Status Specification Review [ 10038 ] Specification [ 10002 ]
          Bertrand Dunogier made changes -
          Status Specification [ 10002 ] Backlog [ 10000 ]
          Bertrand Dunogier made changes -
          Status Backlog [ 10000 ] Specification [ 10002 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Bertrand Dunogier made changes -
          Status Specification [ 10002 ] Specification Done [ 10003 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Bertrand Dunogier made changes -
          Status Specification Done [ 10003 ] Development [ 3 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 1 [ 101 ]
          Sylvain Guittard made changes -
          Rank Ranked higher
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 1 [ 101 ]
          Sylvain Guittard made changes -
          Rank Ranked higher
          Sylvain Guittard made changes -
          Story Points 3 13
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 2 [ 102 ]
          Bertrand Dunogier made changes -
          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}}.

          h3. Backward compatibility
          This should behave like ezplatform-http-cache, where compiler passes will disable the kernel services that are provided by this new package.
          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}}.

          h3. Backward compatibility
          This should behave like ezplatform-http-cache, where compiler passes will disable the kernel services that are provided by this new package.
          Bertrand Dunogier made changes -
          Status Development [ 3 ] Development Done [ 5 ]
          Fix Version/s 2.2.0 [ 14859 ]
          Bertrand Dunogier made changes -
          Status Development Done [ 5 ] Development [ 3 ]
          Andrzej Longosz made changes -
          Story Points 13 5
          Bertrand Dunogier made changes -
          Link This issue relates to EZP-29069 [ EZP-29069 ]
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 2 [ 102 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 3 [ 103 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 3 [ 103 ] [2.2] Sprint 4 [ 104 ]
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 4 [ 104 ] [2.2] Sprint 5 [ 105 ]
          Sylvain Guittard made changes -
          Sprint [2.2] Sprint 5 [ 105 ]
          Sylvain Guittard made changes -
          Rank Ranked higher
          Sylvain Guittard made changes -
          Sprint [2.3] Sprint 1 [ 107 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Gunnstein Lye made changes -
          Fix Version/s 2.2.1-rc1 [ 14998 ]
          Fix Version/s 2.2.0 [ 14859 ]
          Andrzej Longosz made changes -
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ] Andrzej Longosz [ andrzej.longosz@ez.no ]
          Andrzej Longosz made changes -
          Fix Version/s 2.3.0 [ 14910 ]
          Fix Version/s 2.2.1-rc1 [ 14998 ]
          Roland Benedetti made changes -
          Sprint [2.3] Sprint 1 [ 107 ]
          Roland Benedetti made changes -
          Rank Ranked higher
          Roland Benedetti made changes -
          Sprint Candidates for next sprint [ 109 ]
          Sylvain Guittard made changes -
          Sprint Candidates for next sprint [ 109 ] [2.4] Sprint 5 [ 113 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Sylvain Guittard made changes -
          Sprint [2.3] Sprint 5 [ 113 ] Candidates for next sprint [ 109 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Sylvain Guittard made changes -
          Sprint Candidates for next sprint [ 109 ] [2.4] - Sprint 1 [ 115 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Michał Szołtysek made changes -
          Fix Version/s 2.3.0 [ 14910 ]
          Sylvain Guittard made changes -
          Sprint [2.4] - Sprint 1 [ 115 ] [2.4] - Sprint 2 [ 116 ]
          Sylvain Guittard made changes -
          Story Points 5 1
          Sylvain Guittard made changes -
          Sprint [2.4] - Sprint 2 [ 116 ] [2.4] - Sprint 3 [ 117 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Andrzej Longosz made changes -
          Remote Link This issue links to "PR ezsystems/ezplatform-richtext#1 (Web Link)" [ 18659 ]
          Andrzej Longosz made changes -
          Remote Link This issue links to "PR ezsystems/ezplatform-richtext#2 (Web Link)" [ 18660 ]
          Andrzej Longosz made changes -
          Remote Link This issue links to "PR ezsystems/ezplatform-richtext#3 (Web Link)" [ 18661 ]
          Andrzej Longosz made changes -
          Remote Link This issue links to "PR ezsystems/ezplatform-richtext#5 (Web Link)" [ 18662 ]
          Andrzej Longosz made changes -
          Remote Link This issue links to "PR ezsystems/ezpublish-kernel#2302 (Web Link)" [ 18663 ]
          Andrzej Longosz made changes -
          Status Development [ 3 ] Development Done [ 5 ]
          Dominika Kurek made changes -
          Status Development Done [ 5 ] Documentation [ 10010 ]
          Sylvain Guittard made changes -
          Sprint [2.4] - Sprint 3 [ 117 ] [2.4] - Sprint 4 [ 118 ]
          Sylvain Guittard made changes -
          Rank Ranked lower
          Michał Szołtysek made changes -
          Status Documentation [ 10010 ] Documentation Done [ 10040 ]
          Assignee Andrzej Longosz [ andrzej.longosz@ez.no ]
          Michał Szołtysek made changes -
          Status Documentation Done [ 10040 ] QA [ 10008 ]
          Assignee Michał Szołtysek [ michal.szoltysek@ez.no ]
          Michał Szołtysek made changes -
          Status QA [ 10008 ] QA Done [ 10007 ]
          Fix Version/s 2.4.0-beta1 [ 15089 ]
          Assignee Michał Szołtysek [ michal.szoltysek@ez.no ]
          Andrzej Longosz made changes -
          Status QA Done [ 10007 ] Closed [ 6 ]
          Fix Version/s 2.4.0 [ 15091 ]
          Resolution Done [ 9 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Bertrand Dunogier
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile