-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unknown variant rich_text
#170
Comments
Seems there might be some documentation for it in the form of this Java library: https://javadoc.io/static/com.slack.api/slack-api-model/1.0.7/com/slack/api/model/block/element/RichTextElement.html Edit: You can also use it in Slack's "Block Kit Builder" where it is supported: https://app.slack.com/block-kit-builder/T0G5PM4NR#%7B%22blocks%22:%5B%7B%22type%22:%22rich_text%22,%22block_id%22:%22%3Committed%3E%22,%22elements%22:%5B%7B%22type%22:%22rich_text_section%22,%22elements%22:%5B%7B%22type%22:%22text%22,%22text%22:%22foobar%22%7D%5D%7D%5D%7D%5D%7D |
Hi Mattsi! Just noticed this, I'll work on adding support for this tomorrow! 😃 |
Good stuff 👍 For what it's worth I've since discovered other undocumented parts of the Blocks API, like the I've been hacking together my own minimal implementation here that includes these non-documented types, if it helps as a reference: https://github.com/Mattsi-Jansky/termibot/tree/rewrite-in-rust/client/src/models/blocks |
Sorry I dropped this! Added a minimal change to unblock this issue. May be worth considering adding a fallthrough variant as well to be more forward-compatible with Blocks changes going forward |
I'm hitting some issues when parsing valid blocks sent back from the Slack API because they include
type
ofrich_text
which doesn't appear to be supported. And I'm struggling to find it anywhere in the Slack blocks documentation, so it might be undocumented?Specifically, the error:
And the Slack message, which is a response from the
api/chat.postMessage
action, some identifying details omitted:The text was updated successfully, but these errors were encountered: