Theme / styling with settings()
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 41
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 16
Description
- Use
classeslike Svelte UX to pass class to underlying components - Add
createTheme()support - Add
.ComponentNameclasses - Use
const { format } = settings()/$formatinstead offormatNumber()/formatDate()directly - Remove
colorprop (userScaleandfill/stroke/class/style?- Bars
- Points
- Pie
- Link
- Highlight
- Support design tokens (css variables) (see Svelte UX issue)
- Should wait till the Svelte UX issue is resolved
- Remove all use of
var(--color-xxx-xxx). Default tofill-accent-500when possible (or possiblyclass="[--color:theme(colors.blue.500)]"
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.
Research direction
Start by reviewing the unchecked items in this issue and the referenced Svelte UX issue about design tokens. Identify the component entry points affected by classes, createTheme(), and settings() usage; the work is done when the remaining checklist items are implemented consistently and the existing color and design-token behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100