Conversation
Review Summary by QodoAdd ankh-icon component with Material Symbols font and accessibility support
WalkthroughsDescription• Add ankh-icon component with Material Symbols font rendering • Implement accessibility features for decorative and meaningful icons • Add comprehensive unit and a11y tests with vitest-axe • Introduce typecheck workflow and improve CI/CD pipeline • Document icon rendering strategy and versioning guidelines Diagramflowchart LR
A["ankh-icon Component"] --> B["Material Symbols Font"]
A --> C["Size Variants"]
A --> D["Fill Variant"]
A --> E["Accessibility"]
E --> E1["Decorative Icons"]
E --> E2["Meaningful Icons"]
F["Tests"] --> F1["Unit Tests"]
F --> F2["A11y Tests"]
G["CI/CD"] --> G1["Typecheck Workflow"]
G --> G2["Updated PR Template"]
File Changes1. src/components/ankh-icon/ankh-icon.tsx
|
Code Review by Qodo
1. SemVer impact not stated
|
| ## SemVer Impact | ||
|
|
||
| <!-- Which version bump does this PR require? Check one. --> | ||
|
|
||
| - [ ] **Patch** – backwards-compatible bug fix | ||
| - [ ] **Minor** – new feature, new component, or new public prop (backwards-compatible) | ||
| - [ ] **Major** – breaking change to an existing public API | ||
| - [ ] **None** – docs, CI, refactor, or other non-release change |
There was a problem hiding this comment.
1. Semver impact not stated 📘 Rule violation ✓ Correctness
This PR introduces a new public component (<ankh-icon>), but the PR description does not declare the required SemVer impact (patch/minor/major/none). This makes it unclear how consumers should version and can lead to incorrect releases.
Agent Prompt
## Issue description
The PR introduces a new public API surface (`<ankh-icon>`), but the PR description does not declare the SemVer impact.
## Issue Context
The repository now includes a PR template section for SemVer impact, and compliance requires that PR notes document SemVer impact for public API changes.
## Fix Focus Areas
- .github/PULL_REQUEST_TEMPLATE.md[5-12]
- README.md[37-45]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1900ee346c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| * Material Symbols icon font with token-mapped sizing | ||
| */ | ||
|
|
||
| @layer components { |
There was a problem hiding this comment.
Remove @layer wrapper around icon styles
Wrapping the full icon stylesheet in @layer components (src/components/ankh-icon/ankh-icon.css) lowers all of these rules below any unlayered consumer CSS in cascade order, so common app-level resets such as span { font-family: ...; line-height: ...; } can override .ankh-icon and cause ligature text to render instead of Material Symbols glyphs. This is a functional regression for consumers that already ship unlayered global styles; the component base rules should not be placed in a layer unless the entire library is consistently layered.
Useful? React with 👍 / 👎.
Summary
Changes
Notes