Oddity with JSON response to next

[Anniepoo]

I'm sending next events as x-prolog with body

next

and getting back this strange beastie when it goes to destroy:

{
  "data": {
    "data": [{"X": "c"}],
    "event": "success",
    "id": "4c53430f-9570-4e05-9036f6b5fc63dd8c",
    "more": false,
    "time": 3.951999999999992e-05
  },
  "event": "destroy",
  "id": "4c53430f-9570-4e05-9036-f6b5fc63dd8c"
}

I'd count this as an oddity.

[JanWielemaker]

This is fine. Create and destroy events may embed the first and last answer. The first happens if
you include the ask option in the create and the latter if auto destruction is enabled (default). Both
can be combined, which may give you a single response that consists of a create, embedded destroy and embedded first-and-only answer. This is done to reduce round trips.

[Anniepoo]

I understand why its dine, its the field naming - data field with data field - that is odd