{"shas":[["e2aff7ad561029e3b7699d054cb49d569846efee","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add display name for field\n\nThis is to enable having nice names for fields that can be displayed in editors.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["8fba4a74fc4a46bfeef008778b25cb078222bb51","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Field should be capable to add multiple custom validators\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["3cec8708215ccd418d2a9b28caa6c7a34fab4acc","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add param support to all template generation\n\nThis will help users to pass fairly static parameter to a template generation script. For example,\nhow many columns in a table of images, max allowed integer for validation etc.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["b4c79538adb4840a6ec4d7c1abcd055536102b9c","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add test case to validate multiple validators with params work\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["6e44062c32b4791c5b0ad770efbf2725cbd1da1a","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add test case verifying that params are passed properly to variation generators\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["4a2c36b3272f696a9e91b17561def52a758df805","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add test case verifying params are passed to representations\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["05be00112314817d8ef5eaacc9dad421357f1080","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Issue #58 - Representation definition and status should also be inheritable\n\nIf no content status is in either this type or in its parent hierarchy then a 'default' status\nreturned. Representation definitions are merged from parent and can be overriden.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["3e55dbebb1c6a22b4db84b7dd650531f98f91efc","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add API, schema grammer and sample content type definition for composite field\n\nNext step would be to -\n- Parse composite field definition\n- Save composite field definition\n- Retrieve composite field definition\n- Allow content creation, hence add JSON conversion\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["e9dd42fb593dac63013cef3814a7a8095c4d1574","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Parse composite field from content type xml definition\n    \nMostly uses the old parsing code in the form recursion. Test verifies that\ncorrect number of fields are parsed, the hierarchy is ok.\n\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["86d5dbcae5bb9422c59753f507fdefae8ff95636","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Enhance parsing test case to include some other combinations of composition\n\nNotable the composition where another content type is simply embeded and\nthe other case being where there is no embedded content.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["5a4cadacc11a1c1ad1c4ee60993fcc4bc02e6b7a","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add convenience fieldMap for composed field value\n\nThis will primarily assist in templates to access the fields directly by name\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["b7ff8fa16627a52f019aca4e7796061c3766f42a","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Rename factory methods for composition data type definition to 'create'\n\nThis is primarily to keep it coherent with other factory methods related to similar\ntasks.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["0ba6b9be7a0f85fbdf043cc5b7e48054ca98b515","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","First implementation of persisting composite field definition\n\nThe changes have not broken any old tests but it needs to be tested whether\nit works correctly for composite fields. Thus next is the the test cases to check\nthat persistence works.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["77f7d4508f5c104bcc47a5535292f572cbecd16d","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add test case for checking persistence of composite field in content type\n\nIn process had to perform some fixes in the code for composite field persistence\n * Add 'fields' to suffix of the composite field testing\n * 'CONTENT' is added twice for embedded content type, remove one of them\n * Add composed field instead of the parent field in composition data type\n\nNext steps are to -\n * Expose composite fields properly through web service's atom feed\n * Composed field validation should work from inside to outside\n * Indexing of composed field in a content\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["cd8cb1e001980c45f1058ae591b921b09ced80fb","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Refactor to have a single fillSpecialFields method\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["f5de8af809a304980838c6b30f95d1122312c5b2","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Expose composition definition through content type feed resource's entity\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["6b4aa42a55ddc53f79bcc0ff144d718beae5b861","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Composite field value can now converted to JSON\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["98d847d5a07aad9dfeb2aab7fb3fae620044a09c","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","(De)Serialize composite field values to JSON\n\nBasically the JSON representation will be persisted against the composite field in\nHBase. For this add getJsonNode to collection field which returns an object to\nleave it to the implementation to specify what type of object or what library will\nbe used. In this case use ArrayNode and ObjectNode for collection and composite\nfields respectively.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["185ec205705ca8fb91d668d78dacb421364435b8","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Index composite fields with a '.' separator\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"],["38b6c297903251e4fa881322f05c4f98e633a40e","bb5621ada9f40b1f5c463d8e9c51c12e465afec7@smartitengineering.com","Add HTML Form submission for composite fields\n\nFor adding composite fields simply use a '.' separator. For example, if there is an\naddress composite field, composed of, e.g., city and zipcode, then HTML form\nshould have the name address.city and address.zipcode. If its collection of\ncomposite fields then it should be address.0.city, address.0.zipcode, address.1.-\n-city, address.1.zipcode; where 0, 1 are group keys. The field name's should be\nembedded in thus manner.\n\nSigned-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>","Imran M Yousuf"]],"ref":"refs/heads/master","size":35,"head":"647b17291896151522bdd51a4fd810a4905b1af7","push_id":33302335}