Conversation
WalkthroughThis PR introduces a new Alert component to the Eclipse design system with four semantic variants, integrates it into the documentation site for custom callout rendering, and adds comprehensive documentation with usage examples and accessibility guidance. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
🍈 Lychee Link Check Report3660 links: ❌ Errors
Full Statistics Table
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/docs/source.config.ts`:
- Around line 66-75: The types mapping has tip set to "info" but the
Callout/docs treat `tip` as `success`; update the `types` object in
apps/docs/source.config.ts so the `tip` key maps to "success" (i.e., change the
`tip: "info"` entry to `tip: "success"`) and verify other callout keys (e.g.,
`danger`, `warn`, `error`) remain consistent with the docs; if the docs are
intended to change instead, update the docs/callout mapping to match the current
`tip: "info"` value instead.
| types: { | ||
| note: "info", | ||
| tip: "info", | ||
| info: "info", | ||
| warn: "warning", | ||
| warning: "warning", | ||
| danger: "error", | ||
| success: "success", | ||
| ppg: "ppg", | ||
| error: "error", |
There was a problem hiding this comment.
Align tip mapping with Callout/docs semantics.
Line 68 maps tip → "info", but the Callout mapping and docs treat tip as success. That will render :::tip as PPG/info. Please align either the config or the docs/mapping.
🔧 Suggested fix (if docs/callouts are the source of truth)
- tip: "info",
+ tip: "success",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/docs/source.config.ts` around lines 66 - 75, The types mapping has tip
set to "info" but the Callout/docs treat `tip` as `success`; update the `types`
object in apps/docs/source.config.ts so the `tip` key maps to "success" (i.e.,
change the `tip: "info"` entry to `tip: "success"`) and verify other callout
keys (e.g., `danger`, `warn`, `error`) remain consistent with the docs; if the
docs are intended to change instead, update the docs/callout mapping to match
the current `tip: "info"` value instead.
Summary by CodeRabbit
New Features
Documentation