chore(kno-12198): fix callout to use type prop#1362
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
|
|
||
| <Callout | ||
| emoji="💡" | ||
| type="info" |
There was a problem hiding this comment.
Callout type mismatch: info used for warning content
Low Severity
This Callout uses type="info" but its content warns about a side effect — sandbox mode silently prevents channel conditions from being evaluated, and tells users to disable sandbox mode for conditions to take effect. Per the project's Callout validation rules, content that warns about potential problems or side effects fits type="warning" rather than type="info".
There was a problem hiding this comment.
I think this is appropriate as info. This callout describes expected behavior. We recently had a customer face confusion trying to use these things together, so this callout is an attempt to make the information more visible.
1 participant
Summary
content/integrations/overview.mdxto usetype="info"instead ofemoji="💡". Using a custom emoji without a type drops the background color.Changes
content/integrations/overview.mdx—emoji="💡"→type="info"on channel conditions callout