[MGNLPN-302] Introduce a mechanism to get all personalised descendants of a node Created: 11/Jul/16  Updated: 25/Jul/16  Resolved: 15/Jul/16

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

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLPN-300 Disable caching of pages with compone... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Kromeriz 53
Story Points: 3

 Description   

Introduce method to get all personalised descendants which is currently widly used after introduction of component personalization.
This method is not component personalization specific due to these reasons:

  1. Might be used later for content app personalization.
  2. Allow us to get rid of component personalisation specific code (such as page title column formatter, cache voter)

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