Components v2#7487
Conversation
There was a problem hiding this comment.
The following message is repeated really often:
> info
> To use this component, you need to send the [message flag](/docs/resources/message#message-object-message-flags) `1 << 15` (IS_COMPONENTS_V2) which can be activated on a per-message basis.
Might it be better to just specify a version number in the heading, linking to "this needs flag xy"?
Anyways, I really love how the docs turned out. Might've overseen something. Will look a bit later again.
The suggestions should catch most > info parts and change them to :::info as Justin mentioned.
Also discussion point: Putting IS_COMPONENTS_V2 into ` IS_COMPONENTS_V2
Since I was asked to review
| | 13 | [File](/docs/components/reference#file) | Displays an attached file | Content | Message | | ||
| | 14 | [Separator](/docs/components/reference#separator) | Component to add vertical padding between other components | Layout | Message | | ||
| | 17 | [Container](/docs/components/reference#container) | Container that visually groups a set of components | Layout | Message | |
There was a problem hiding this comment.
I assume we decided against including the content inventory type (it can be received) as reference?
Icebluewolf
left a comment
There was a problem hiding this comment.
Just wanted to point out a few things I saw :)
Sorry, if these are overly nit-picky.
Lulalaby
left a comment
There was a problem hiding this comment.
Additionally, since it came up again on our lib server: It should be mentioned that components (namely text display) can mention users and roles.
07ceead to
51517d4
Compare
f5c4486 to
17d4a35
Compare
JustinBeckwith
left a comment
There was a problem hiding this comment.
"just let me sneak one more merge conflict in first"
|
dammit it too late |
Adding documentation, changelog, and links updates for components v2. The interactions.js library and samples using it are going to follow in another PR.