[MAGNOLIA-2228] Convenience methods in Content to deal with localized node data Created: 06/Jul/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Improvement Priority: Minor
Reporter: Philippe Marschall Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File Content.java     Text File Content.java.patch     Text File DefaultContent.java     Text File DefaultContent.java.patch    
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   

The introduction of i18n content support made dealing with node data a lot more cumbersome. What once was:

node.getNodeData(name)

became:

I18nContentSupportFactory.getI18nSupport().getNodeData(node, name)

my proposal is to reduce this to:

node.getLocalizedNodeData(name)

patch attached



 Comments   
Comment by Philipp Bracher [ 08/Jul/08 ]

In jsps you should use the cms:out tag which does that for you. For the sake of separation I would prefer a util class. But I see the the benefit in the sense of usability.

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:34:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.