[MGNLPN-490] Carefully deprecate all the functionality that was superseded by the UI framework update (follow-up) Created: 25/Mar/20  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLPN-487 Carefully deprecate all the functiona... Closed
Issue split
split to MGNLPN-489 Implement IsPersonalizable availabili... Open
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: UI framework implementation

 Description   

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).


Generated at Mon Feb 12 06:38:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.