Val3dity Report Inconsistency

[Lkeurentjes]

just came across it in the val3dity report in the features array there is an inconsistency when parrent child are added together (for example with a 3dbag tile). The primitves of the parrent have no "errors" when empty but the children do, for example:

{
      "errors": [],
      "id": "NL.IMBAG.Pand.1667100000000009",
      "primitives": [
        {
          "id": "0",
          "numberfaces": 1,
          "numbervertices": 15,
          "type": "MultiSurface",
          "validity": true
        },
        {
          "errors": [],
          "id": "1",
          "numberfaces": 17,
          "numbershells": 1,
          "numbervertices": 30,
          "type": "Solid",
          "validity": true
        },
        {
          "errors": [],
          "id": "2",
          "numberfaces": 17,
          "numbershells": 1,
          "numbervertices": 30,
          "type": "Solid",
          "validity": true
        },
        {
          "errors": [],
          "id": "3",
          "numberfaces": 46,
          "numbershells": 1,
          "numbervertices": 69,
          "type": "Solid",
          "validity": true
        }
      ],
      "type": "Building",
      "validity": true
    },

So when reading it ends up a nullptr instead of an empty array.
(when there are errors, "errors" does pop up, so no problems then)