post to /circulation/requests without request date returns error but changes item status

UPDATE (2021-10-04):

This issue appears to have gotten lost. I've confirmed that the reported behavior still exists and actually occurs if the fulfilmentPreference value is incorrect, as well. For example:

Attempt to post the following payload to folio-snapshot to replicate the originally-reported behavior:

{
    "requestType": "Page",
    "fulfilmentPreference": "Hold Shelf",
    "requesterId": "bec20636-fb68-41fd-84ea-2cf910673599",
    "itemId": "23fdb0bc-ab58-442a-b326-577a96204487",
    "pickupServicePointId": "3a40852d-49fd-4df2-a1f9-6e2641a6e91f"
}

Ensure that the item with barcode: 653285216743 is in status "Available"

To replicate the issue with "fulfilmentPreference", attempt to post this payload:

{
    "requestType": "Page",
    "fulfilmentPreference": "Hold shelf",
    "requesterId": "bec20636-fb68-41fd-84ea-2cf910673599",
    "itemId": "23fdb0bc-ab58-442a-b326-577a96204487",
    "pickupServicePointId": "3a40852d-49fd-4df2-a1f9-6e2641a6e91f"
}

Again, make sure the item is in status "Available"

ORIGINAL REPORT

If you attempt to create a request without a request date the service returns an error and does NOT create the request but it does change the item status to Paged (for a previously 'available' item)

To recreate:
POST to
http://localhost:9130/circulation/requests
using an available item without a 'requestDate':

The return is:

{
"errors": [{
"message": "may not be null",
"type": "1",
"code": "-1",
"parameters": [

]
}]
}

However, the item status is changed to Paged