[MAGNOLIA-4518] Unnecessary calls to unwrap JCRPropertiesFilteringNodeWrapper are still present in the code Created: 24/Aug/12 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.5 |
| Fix Version/s: | 4.5.x |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| 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)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Description |
|
as of SCRUM-405 we no longer wrap Nodes in JCRPropertiesFilteringNodeWrapper and don't hide jcr specific props. However there's still plenty of places in the code that attempt to unwrap said wrapper before using nodes, e.g. DefaultContent, DefaultHierarchyManager, NodeUtil, VersionUtil. |