Reimplement datepicker component without using PrimeNG
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- angular, typescript
- Domain
- frontend
Research direction
Start by searching the repository for datepicker and primeng references to locate the existing component and its module wiring. Read those component files plus any shared-module exports/entry points to map where it is consumed, then check any existing tests or examples tied to it. Remove the PrimeNG dependency from that component path and verify behavior via the existing tests/build checks. Done when the datepicker is implemented without PrimeNG for that component and checks pass.
Written by the indexing model from the issue text.
Description
This issue has no description.
- 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 1/5 Under an hour Newbie friendliness 72/100
yjh051108/dsh-routing-suite#216 ·
-
kind/bug priority/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Dependencies view: `getParent` loops forever on untitled documents, extension host runs out of memoryPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 Half a day Newbie friendliness 66/100
apache/fineract-consumer-facing#175 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 Under an hour Newbie friendliness 82/100
awslabs/visual-asset-management-system#413 ·
Maintainers usually reply within 1 day