Skip to content

refactor(block-kit): remove nested rich_text block example in favor of standalone elements - #248

Draft
zimeg wants to merge 1 commit into
mainfrom
rm-nested-rich-text
Draft

refactor(block-kit): remove nested rich_text block example in favor of standalone elements#248
zimeg wants to merge 1 commit into
mainfrom
rm-nested-rich-text

Conversation

@zimeg

@zimeg zimeg commented Sep 8, 2026

Copy link
Copy Markdown
Member

Summary

Removes the nested rich_text block example (blocks/rich_text) from the block-kit examples, keeping the standalone rich-text element examples (elements/rich_text_*) that the docs reference pages now point at directly.

Why

The docs rich_text element reference pages (section / list / preformatted / quote / input) each pin their SDK example tabs to the standalone elements/rich_text_* files. The rich_text block page is prose-only and references no example file. The nested blocks/rich_text example was a full duplicate of those standalone element examples — kept provisionally until the docs landed pinning to the standalone files (they did, via slackapi/docs#795).

Every nested exampleNN is reproduced by a standalone element example (verified payload-for-payload), so this is pure deduplication, no loss of demonstrated coverage:

nested standalone equivalent
example01 rich_text_section
example02 / 03 rich_text_list
example04 rich_text_preformatted
example05 rich_text_quote
example06–13 (broadcast/color/channel/date/emoji/link/user/usergroup) the respective standalone element example

Changes

  • Delete the nested example source + its test
  • Remove the "Rich text" block row from block-kit/README.md (the five rich-text element rows stay — they point at the surviving standalone files)

Tests green with the example removed.

…f standalone elements

The rich_text block example (blocks/rich_text) duplicated the standalone
rich-text element examples (elements/rich_text_*), which the docs reference
pages now pin to directly. Every nested exampleNN is reproduced by a
standalone element example, so this is pure deduplication with no loss of
demonstrated coverage:

- example01 -> rich_text_section
- example02/03 -> rich_text_list
- example04 -> rich_text_preformatted
- example05 -> rich_text_quote
- example06-13 (broadcast/color/channel/date/emoji/link/user/usergroup)
  -> the respective standalone element examples

The rich-text-block reference page is prose-only and references no example
file, so removing this changes no docs reference.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@zimeg zimeg self-assigned this Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant