You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Spacious message promotions
* Compact message promotions
* Promotions callback handler, tests, md links in new tab.
* Promotion link as external learnmore
* Cleanup
* Add stories for promotions, make link inline, update README
* Run changeset
* Update README based on recent changes
* Run linter
* Apply suggestions from code review
Co-authored-by: Stephen Lee <[email protected]>
* PR review: README improvements
* PR review: Remove promotions from spacious msg variant
* PR review: styling, Badge component, test with Chromatic, rm unused items
* Require promotion URL
* Actually support promotions darkmode [REAL]
* Center text / badge
* Rename onPromotionClick and Update message README
* Fix table
* Removing obvious info from README
* Removing obvious info from README
---------
Co-authored-by: Stephen Lee <[email protected]>
Copy file name to clipboardExpand all lines: chat/message/README.md
+47-1Lines changed: 47 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ return (
61
61
62
62
### Compound Components
63
63
64
-
The `Message` component uses a compound component pattern, allowing you to compose different parts of a message using subcomponents like `Message.Actions`, `Message.Links`, and `Message.VerifiedBanner`.
64
+
The `Message` component uses a compound component pattern, allowing you to compose different parts of a message using subcomponents like `Message.Actions`, `Message.Links`, `Message.Promotion`, and `Message.VerifiedBanner`.
65
65
66
66
**Note 1:** All compound components only render in the `compact` variant.
67
67
**Note 2:** The layout and order of compound components are enforced by the `Message` component itself. Even if you change the order of subcomponents in your JSX, they will be rendered in the correct, intended order within the message bubble. This ensures consistent UI and accessibility regardless of how you compose your message children.
0 commit comments