Skip to content

not covered/not specified yet: diff incl. id update #4

Description

@julia05

id update creates a delete and add difference

The question is, should only the add - add be a conflict or also delete - add and add - delete?

2 unit tests in up-up.test.ts

  • smart city class property id update -> up-up conflict
  • reference from smart city outgoing to Component/Project/Category with reference id update -> up-up conflict

Example
Left:

{
  op: "delete",
  path: "/package/classes/0/references/0",
  value: {
    id: "name1",
    containment: true,
    upperBound: -1,
    lowerBound: 0,
    type: {
      $ref: "#/package/classes/3",
    },
  },
},
{
  op: "add",
  path: "/package/classes/0/references/0",
  value: {
    id: "name2",
    containment: true,
    upperBound: -1,
    lowerBound: 0,
    type: {
      $ref: "#/package/classes/2",
    },
  },
}

Right:

{
  op: "delete",
  path: "/package/classes/0/references/0",
  value: {
    id: "name1",
    containment: true,
    upperBound: -1,
    lowerBound: 0,
    type: {
      $ref: "#/package/classes/3",
    },
  },
},
{
  op: "add",
  path: "/package/classes/0/references/0",
  value: {
    id: "name3",
    containment: true,
    upperBound: -1,
    lowerBound: 0,
    type: {
      $ref: "#/package/classes/1",
    },
  },
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions