diff options
author | Trygve Aaberge <trygveaa@gmail.com> | 2023-07-06 22:13:35 +0200 |
---|---|---|
committer | Trygve Aaberge <trygveaa@gmail.com> | 2023-07-07 01:48:31 +0200 |
commit | 74da30342e8d328fc085d2158e37afda3b908f2c (patch) | |
tree | 6c3dd5fd96d56a6cb7653e665ba4c87ee202078b /docs/Options.md | |
parent | 857a42dee093ef87723d0e214a29bc346a29a595 (diff) | |
download | wee-slack-74da30342e8d328fc085d2158e37afda3b908f2c.tar.gz |
Support and use rich_text blocks for message content
Instead of just using the text field of a message, use the rich_text
blocks to format the message.
The main reason for doing this was that messages that include images
suddenly started just having "This message contains interactive
elements." in the text field.
There are some other benefits as well:
- It fixes some bugs with multiple formatting styles not being applied
correctly.
- It fixes links in code blocks not being rendered verbatim (but with
text and url, like outside code blocks).
- It fixes code blocks sometimes having newlines after/before ``` and
sometimes not, depending on how the message was sent.
It looks like messages with images are now back to having the proper
text in the text field (for new messages), so this change isn't
necessary to fix that after all (except for for messages in the history
sent in the last couple of days), but since it fixes other issues as
well, it's best to keep it.
There is one bug left when inline code blocks contains links. Then there
will be ` characters before and after the link, which shouldn't be
there, but I'll leave fixing this for later.
Fixes #354, fixes #550, fixes #893
Diffstat (limited to 'docs/Options.md')
0 files changed, 0 insertions, 0 deletions