{"version":"2.1.228","anchor":"unrenderable-message-errors-no-longer-echo-arbitrary-text","canonical_anchor":"unrenderable-message-errors-no-longer-echo-arbitrary-text","heading":"Unrenderable message errors no longer echo arbitrary text","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/unrenderable-message-errors-no-longer-echo-arbitrary-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Unrenderable message errors no longer echo arbitrary text\n\nThe \"unable to render message\" notice no longer echoes arbitrary text from the message.\n\n**What**\n\nThe \"Unable to render message type\" fallback used to print the raw type value from the message block. It now prints the type only if it is on an allowlist, and otherwise reports `non-allowlisted (non-string)` or just a length.\n\n**Details**\n\n- The allowlist now includes the newly handled `fallback` and `mid_conv_system` types.\n\n**Evidence**\n\n`non-allowlisted (non-string)`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}