HierarchyManager should be an interface (testing and delegating)
(MAGNOLIA-1352)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 3.1 M1 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Comments |
| Comment by Magnolia International [ 02/Apr/07 ] |
|
applied patch from |
| Comment by Philipp Bracher [ 04/Apr/07 ] |
|
This method should be moved to the Path or ContentUtil class |
| Comment by Magnolia International [ 04/Apr/07 ] |
|
i think the point of Oliver's patch was that subclasses could provide their own way of generating the label. And its already using the Path.getUniqueLabel method, just surrounding with some extra logic, that could maybe be refactored indeed. |
| Comment by Philipp Bracher [ 05/Apr/07 ] |
|
OK, sorry for that |