Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4971

Carefully deprecate all the functionality that was superseded by the UI framework update


    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 6.2
    • None
    • None
    • None
    • Yes
    • UI Framework 20
    • 13

      Compatibility artifact: Properly deprecate & point to new classes.

      Better to start with a certain defined cluster of functionality, pick e.g. one of the following:

      • field definitions,
      • action definitions
      • transformers, converters, validators etc

      The ultimate goal is to have everything inside of compatibility artefact deprecated with a clear pointer to the non-deprecated counterpart. In case something appears to not have a clear replacement or even not a subject for deprecation at all, it has to be discussed on the case-by-case and the actions should be taken (follow-ups, extraction of the logic out of deprecated artefact etc).

      Special consideration needs to be applied to deprecated code usage logic (info.magnolia.pages.rendering.registry.validator.DialogAwareTemplateDefinitionValidator and such). We need to provide a way to probably whitelist the definitions coming from compatibility artefact for the time being (for the sake of not polluting the definitions app with noise).

        Acceptance criteria

              mduerig Michael Duerig
              apchelintcev Aleksandr Pchelintcev
              0 Vote for this issue
              4 Start watching this issue


                  Original Estimate - Not Specified
                  Not Specified
                  Remaining Estimate - 0d
                  Time Spent - 1d 7h
                  1d 7h