Implement dark mode support for individual components
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- angular, typescript
Research direction
No file, test, or entry point is identified; begin by locating the implementations for the 33 components named in the checklist and reading any existing theming conventions. Work through the checklist component by component, and consider the issue complete only when every listed component has dark-mode support.
Written by the indexing model from the issue text.
Description
Implement dark mode support for components. Tracking will be handled using the checklist below instead of 33 individual sub‑issues to reduce repository noise.
- Autocomplete
- Button
- Button toggle
- Checkbox
- Chip
- Datepicker
- Dialog
- Divider
- Expansion panel
- File upload
- Icon
- Info circle
- Input
- Loader
- Menu
- Notifications
- Paginator
- Progress circular
- Progress linear
- Radio
- Scheduler
- Select
- Sidebar menu
- Switch
- Table
- Tabs
- Tag
- Textarea
- Timepicker
- Tooltip directive
- Tree autocomplete
- Tree select
- Tree table
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 7
- Avg merge
- 11h 59m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from AbsaOSS/cps-shared-ui
-
enhancement library
Difficulty 1/5 Under an hour Newbie friendliness 85/100
AbsaOSS/cps-shared-ui#644 ·
Maintainers usually reply within 1 day
-
library new component
Difficulty 3/5 Half a day Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#853 ·
Maintainers usually reply within 1 day
-
library new component
Difficulty 3/5 1-2 days Newbie friendliness 62/100
AbsaOSS/cps-shared-ui#792 ·
Maintainers usually reply within 1 day
-
library tech-debt
Difficulty 3/5 1-2 days Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#692 ·
Maintainers usually reply within 1 day
-
library tech-debt
Difficulty 3/5 1-2 days Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#691 ·
Maintainers usually reply within 1 day
All issues in AbsaOSS/cps-shared-ui
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
cline/mcp-marketplace#2932 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#32188 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Portkey-AI/gateway#1844 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
rjsf-team/react-jsonschema-form#5495 ·
Maintainers usually reply within 2 days