Bug 1001435 - Move content spec constants (like "Title") to common library
Summary: Move content spec constants (like "Title") to common library
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact: Matthew Casperson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-27 04:20 UTC by Matthew Casperson
Modified: 2014-08-04 22:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 05:17:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Matthew Casperson 2013-08-27 04:20:34 UTC
Using the content spec REST entities often involves looking up specific metadata nodes. It would be nice if the constant metadata nodes had names in a common library like RESTv1Constants so we could write code like

String title = "";
for (final RESTCSNodeCollectionItemV1 csNode : spec.getItem().getChildren_OTM().getItems()) {
    if (csNode.getItem().getNodeType() == RESTCSNodeTypeV1.META_DATA &&
            csNode.getItem().getTitle().equals(RESTv1Constants.CONTENT_SPEC_METADATA_TITLE)) {
        title = csNode.getItem().getAdditionalText();
        break;
    }
}

Comment 3 Lee Newson 2013-08-28 02:37:13 UTC
Moved the MetaData constants to the CommonConstants class. See https://github.com/pressgang-ccms/PressGangCCMSCommonUtilities/commit/f0895164aae9dac22b86cd8582d3aa33a23be33c


Note You need to log in before you can comment on or make changes to this bug.