Error in $.user: key "deleted" not present

[mbbx6spp]

I get this error message using revision ab91568 of this repository:

Error in $.user: key "deleted" not present
Please report this failure to the github issue tracker

The prettified anonymized JSON payload generating this error is:

{
  "type": "user_change",
  "user": {
    "id": "XXXX5N2F",
    "team_id": "T5XXXXXX",
    "name": "some_user",
    "color": "e7392d",
    "is_bot": false,
    "is_app_user": false,
    "profile": {
      "avatar_hash": "xxxxxx86xxxx",
      "image_original": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_original.jpg",
      "image_24": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_24.jpg",
      "image_32": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_32.jpg",
      "image_48": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_48.jpg",
      "image_72": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_72.jpg",
      "image_192": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_192.jpg",
      "image_512": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_512.jpg",
      "image_1024": "https://avatars.slack-edge.com/2017-11-02/xxxxxx86xxxxecd68cf0_1024.jpg",
      "first_name": "Some",
      "last_name": "Name",
      "real_name": "Some Name",
      "display_name": "some_user",
      "real_name_normalized": "Some Name",
      "display_name_normalized": "some_user",
      "team": "T5XXXXXX"
    },
    "updated": 1561557818
  },
  "cache_ts": 1561557818,
  "channel": "XXXXXDK71",
  "event_ts": "1561557818.356600"
}

Slack API has a deleted key according to these docs:
https://api.slack.com/types/user

The slack-api code is expecting a deleted flag attribute )https://github.com/mpickering/slack-api/blob/master/src/Web/Slack/Types/User.hs#L29) but in the user_change event inclusion of the user entity it does not appear to be sending it. :(

Not sure this should be fixed in slack-api but I wanted to record the ticket and then refer to it for Slack to see if they fix their end or their documentation.

I retained the timestamp data in case it is useful for Slack to troubleshoot if it is a cache issue on their server side.

Cheers.

[mbbx6spp]

I will try to submit a PR later this week (when Slack updates their documents). Thanks.