Uploaded image for project: 'Hippo Repository'
  1. Hippo Repository
  2. REPO-1708

AutoExport: add correct order-before for nodes within first export module

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.1
    • Labels:
      None
    • Similar issues:
    • Story Points:
      2
    • Epic Link:
    • Processed by team:
      Platform
    • Sprint:
      Platform161: Pre-GA1, Platform162: Pre-GA2, Platform163: GA!, Platform164

      Description

      DefinitionMergeService does nothing with .meta:order-before for config nodes that already exist, and it naively copies this property for any newly-created config nodes.

      1. Handle the case of a pure reordering, with no other changes to a config node.
      2. When attempting to add a .meta:order-before to a config node, suppress any reference to nodes that are "downstream" in the module dependency hierarchy – i.e. will not be known to the ConfigurationTreeBuilder when processing the (proposed) .meta:order-before.
      3. When adding (or attempting to add) a .meta:order-before to a config node, update the .meta:order-before of all siblings that are located in other ConfigDefinitions to match the new intended ordering.
      4. Implement new unit tests for these cases and/or update existing tests to include them.

        Attachments

          Activity

            People

            • Assignee:
              lsharma Lakshay Sharma
              Reporter:
              PCentgraf Peter Centgraf
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: