Uploaded image for project: 'Hippo Configuration Management'
  1. Hippo Configuration Management
  2. HCM-208

Don't serialize type (Name) for pre-defined jcr:primaryType and jcr:mixinTypes properties

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 1.0.0
    • Fix Version/s: 1.0.1
    • Labels:
      None
    • Similar issues:
    • Epic Link:
    • Processed by team:
      Platform
    • Sprint:
      Platform164

      Description

      During of parsing or jcr:primaryType and jcr:mixinTypes properties their type (Name) is automatically inferred, so doesn't need to be specified.

      And, as we also don't serialize that type property when no property override is specified a developer actually shouldn't specify the type for these properties otherwise and input/output no longer will align.

      When encountering an override of one these properties however we currently do serialize the type (Name), which is non-consistent and really not needed as during parsing that type is still automatically inferred if not specified. 

      The fix is to also not serialize the type for these properties in case of an override.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adouma Ate Douma
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: