[MAGNOLIA-1787] Refactoring of GroupList/RoleList interfaces Created: 17/Oct/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core, security
Affects Version/s: 3.5 RC1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-2044 Groups are not resolved properly with... Closed
relation
is related to MAGNOLIA-2004 update: Secured URIs menu item not re... 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)
Date of First Response:

 Description   

RoleList is currently a GroupList, and same goes for their respective implementations. The goal simply being to share code, and not to share semantics, they should be refactored into a parent interface and parent abstract class.

This api/package could probably use some more brushing up.



 Comments   
Comment by Magnolia International [ 05/Feb/08 ]

this was started to provide a fix for MAGNOLIA-2004, but could surely be improved with regards to simplicity / clarity of the api or docs.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:30:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.