design-sparx / design-sparx/pattern-base
fix(all): fix invalid types in template literal expressions (~10 instances)
Open
@kelvink96 is already working on this.
Since Sep 19, 2026.
lint
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 23h 44m
- Merged PRs (30d)
- 5
Description
Problem
Multiple packages have @typescript-eslint/restrict-template-expressions warnings where non-string types (numbers, ReactElement, etc.) are interpolated into template literals.
Antd / Bootstrap — ReactElement in template literal
packages/{antd,bootstrap}/src/components/preset-styles/preset-styles.tsx—preset.iconis a ReactElement used in template stringpackages/bootstrap/src/components/modes/modes.tsx—mode.iconis a ReactElement used in template string
Fix: Use String() or extract a text label instead of interpolating ReactElement.
Antd / Bootstrap — Number in template literal
packages/{antd,bootstrap}/src/components/attachments/attachments.tsxpackages/{antd,bootstrap}/src/components/draft-mode/draft-mode.tsxpackages/bootstrap/src/components/filters/filters.tsx
Fix: Ensure number is wrapped with String() or use ${Number} items explicitly.
Mantine — Number in template literal
packages/mantine/src/components/watermark/watermark.tsx
Count
~10 instances.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.