[MGNLPN-487] Carefully deprecate all the functionality that was superseded by the UI framework update Created: 23/Mar/20 Updated: 25/Mar/20 Resolved: 25/Mar/20 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Šimon Demočko |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Epic Link: | UI framework implementation | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| 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:
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). |
| Comments |
| Comment by Šimon Demočko [ 25/Mar/20 ] |
|
Activity rules deprecated and merged. Further deprecations to be continued, parking. |