Repository navigation
Is there any way to use the rich_text_list format when working with blocks? #520
Description
Activity
Hi @Rebwon! Thanks for coming to us with your question 🙌.
rich_text_listis a supported format 😄 here is an example of how you might use it in blocks:blocks=[ { "type": "rich_text", "block_id": "block1", "elements": [ { "type": "rich_text_section", "elements": [ { "type": "text", "text": "Breakfast foods I enjoy:" } ] }, { "type": "rich_text_list", "style": "bullet", "elements": [ { "type": "rich_text_section", "elements": [ { "type": "text", "text": "Hashbrowns" } ] }, { "type": "rich_text_section", "elements": [ { "type": "text", "text": "Eggs" } ] } ] }, { "type": "rich_text_list", "style": "bullet", "indent": 1, "elements": [ { "type": "rich_text_section", "elements": [ { "type": "text", "text": "Scrambled" } ] }, { "type": "rich_text_section", "elements": [ { "type": "text", "text": "Over easy" } ] } ] }, { "type": "rich_text_list", "style": "bullet", "elements": [ { "type": "rich_text_section", "elements": [ { "type": "text", "text": "Pancakes, extra syrup" } ] } ] } ] } ]Which looks like:
Is this the sort of output you're looking for?
Hello,
Our team currently writes release notes in Markdown using GitHub Releases, and we’ve implemented a workflow that uses GitHub Actions with the release: published trigger to send those release notes to Slack.
From what I can tell from the documentation, section and header blocks are supported, but it seems that formats like rich_text_list are not available. Is that correct?
In Markdown, the -, *, and + markers are rendered as lists, but in Slack they are not displayed as lists. Because of this, we would like to parse the GitHub release note message ourselves and convert it into something that uses a rich_text_list-style format when sending it to Slack.
I’d like to ask whether you have any plans to support this kind of list formatting, and whether it is currently possible to achieve this in any way. Thank you.