docs(IllustratedMessage): broaden the component description - #3052
Merged
Jan-Eimertenbrink merged 1 commit intoSep 1, 2026
Merged
Conversation
The old wording tied the IllustratedMessage to a single use case — a placeholder for content that will be replaced later. That framing was too narrow: we also use it for other cases, so describe what it does structurally instead. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Coverage Report for ./packages/components/
File CoverageNo changed files found. |
Lisa18289
approved these changes
Sep 1, 2026
Contributor
🚀 Preview DeploymentPreview environments are ready:
Images:
|
Jan-Eimertenbrink
deleted the
claude/illustrated-message-description-2f6855
branch
September 1, 2026 12:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the short description of the
IllustratedMessagecomponent.Before:
After:
Why
The old wording constrained us too much: it focused primarily on the component being a placeholder for content that is shown later. But we have other use cases as well, so the description now says what the component does structurally rather than pinning it to that single scenario.
🤖 Generated with Claude Code