Current Behavior
Sistent's icon exports are valid today, but several names differ from the more common *Icon convention that downstream callers and reviewers often expect.
For example, the package currently exports names like:
AccessTimeGroupAddInfoOutlinedLinkBarchartIcon
During downstream Meshery work, these exports were repeatedly flagged as suspicious because consumers expected names like AccessTimeIcon, GroupAddIcon, InfoOutlinedIcon, LinkIcon, and BarChartIcon.
Desired Behavior
Add backward-compatible alias exports for these icons so both naming styles work:
AccessTimeIcon -> alias of AccessTimeGroupAddIcon -> alias of GroupAddInfoOutlinedIcon -> alias of InfoOutlinedLinkIcon -> alias of LinkBarChartIcon -> alias of BarchartIcon
Why this helps
- Reduces downstream confusion and false-positive review comments.
- Better matches the dominant icon naming convention used across React/MUI ecosystems.
- Keeps the change additive and non-breaking for existing consumers.
Notes
- This is not a request to remove the current exports.
- The request is only to add aliases for compatibility and ergonomics.
- Related context: Meshery had to verify these names manually while reviewing
@sistent/sistent usage.
Current Behavior
Sistent's icon exports are valid today, but several names differ from the more common
*Iconconvention that downstream callers and reviewers often expect.For example, the package currently exports names like:
AccessTimeGroupAddInfoOutlinedLinkBarchartIconDuring downstream Meshery work, these exports were repeatedly flagged as suspicious because consumers expected names like
AccessTimeIcon,GroupAddIcon,InfoOutlinedIcon,LinkIcon, andBarChartIcon.Desired Behavior
Add backward-compatible alias exports for these icons so both naming styles work:
AccessTimeIcon-> alias ofAccessTimeGroupAddIcon-> alias ofGroupAddInfoOutlinedIcon-> alias ofInfoOutlinedLinkIcon-> alias ofLinkBarChartIcon-> alias ofBarchartIconWhy this helps
Notes
@sistent/sistentusage.