Conditional delete operation outcome has nulls in issue details

[JohnTimm]

I recently created 3 Patient resources each using a standard create interaction (POST) all with the same Patient.identifier element. I then did a search:

GET <base>/fhir-server/api/v4/Patient?identifier=12345

and I get a Bundle resource containing 3 patients. Then I tried using the "conditional delete" interaction:

DELETE <base>/fhir-server/api/v4/Patient?identifier=12345

and I got the following response:

{
    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "information",
            "code": "informational",
            "details": {
                "text": "Deleted 3 Patient resource(s) with the following id(s): null,null,null"
            }
        }
    ]
}

Then I confirmed that the resource(s) have been deleted by performing another search:

GET <base>/fhir-server/api/v4/Patient?identifier=12345

{
    "resourceType": "Bundle",
    "id": "4196a09f-c220-4ca2-91c4-9d8e3bbcdd60",
    "type": "searchset",
    "total": 0,
    "link": [
        {
            "relation": "self",
            "url": "https://localhost:9443/fhir-server/api/v4/Patient?_count=10&identifier=12345&_page=1"
        }
    ]
}

The "conditional delete" behavior works as advertised but there should be actual resource ids in the operation outcome instead of nulls.

[JohnTimm]

After this was merged, I ran a the following test to verify it:

DELETE <base>/fhir-server/api/v4/Patient?identifier=12345

and this was the result:

{
    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "information",
            "code": "informational",
            "details": {
                "text": "Deleted 1 Patient resource(s) with the following id(s): 12345"
            }
        }
    ]
}