[MAGNOLIA-6624] Introduce GroupManager #getAllSuperGroups and #getAllSubGroups Created: 07/Apr/16  Updated: 09/Feb/17  Resolved: 22/Jul/16

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

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: api
Remaining Estimate: 0d
Time Spent: 1d 1h
Original Estimate: 2d

Issue Links:
causality
supersession
supersedes MAGNOLIA-6615 UserManager#getUsersWithGroup(groupNa... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Sprint: Saigon 53
Story Points: 2

 Description   

In MAGNOLIA-6615, we agreed to differentiate and introduce #getAllSuperGroups and #getAllSubGroups. We only did so on MgnlGroupManager concrete impl, for binary compatibility reasons.

With 5.5, we introduce this into the GroupManager interface straight. We move the javadoc up a level, and then deprecate GroupManager#getAllGroup, which was ambiguous.

We might as well address other few points from the related concept (sections 1b, 2, 3 and 6) if there's any easy target, or keep that as other follow-ups.


Generated at Mon Feb 12 04:16:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.