Theme / styling with settings()

Open
#39 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
css, typescript
Domain
design, frontend

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.

Description

  • Use classes like Svelte UX to pass class to underlying components
  • Add createTheme() support
  • Add .ComponentName classes
  • Use const { format } = settings() / $format instead of formatNumber() / formatDate() directly
  • Remove color prop (use rScale and fill / 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 to fill-accent-500 when possible (or possibly class="[--color:theme(colors.blue.500)]"
Dominant language
TypeScript
Stars
1.3k
Forks
41
Avg merge
2d 8h
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from techniq/layerchart

All issues in techniq/layerchart

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.