Valid message is rendered as broken

[dozro]

Describe the bug

The following message is rendered as broken message

{
  "content": {
    "body": "",
    "msgtype": "m.text"
  },
  "origin_server_ts": 1773182126392,
  "sender": "@rye:fairchat.eu",
  "type": "m.room.message",
  "unsigned": {
    "membership": "join",
    "age": 337,
    "transaction_id": "m1773182126184.46"
  },
  "event_id": "$QUbSte-uYnuoBtDFcW7Ye4Z1o31k9sz7JvR7hA0O1ac",
  "room_id": "!a6sXbRuOyyc7MKutmy:sable.moe"
}

it should be a valid message, maybe display it as "empty message" or something, but not as broken

Reproduction

No response

Expected behavior

No response

Platform and versions

Sable: v1.6.0 (d9a8dae)

Additional context

No response

[Rosy-iso]

what does the spec say

[dozro]

good question, i will need to look that up
@nexy7574 meant in the discussion on matrix yesterday that an empty body should be allowed, while an absent body shouldn’t

Edit: As far as I read the spec an empty body is allowed. It's not really ideal, but it is allowed.

[leamikmik]

Also getting this error on a message with an empty body but a non-empty formatted_body

[nexy7574]

The spec mandates that body is present, not that it is populated. For example, an image without a caption will have "body": "" to denote that there is no caption. Regular text messages can also be empty if the user chooses not to send any text.

[dozro]

closed with #234