Polish fractional-cent display and invalid expense navigation
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reading the monthly expense fix and the second review of #52, then trace the wizard’s monetary inputs and unit switching. Check how annual amounts below one cent per month, pasted fractional-cent values, and invalid entries behave; preserve underlying values and shared links. Done means those display and validation choices are consistent and the existing typing and invalid-rent regressions still pass.
Written by the indexing model from the issue text.
Description
The monthly expense fix preserves partial decimals while typing and annual values on submission. Three optional input details from the second review of #52 remain:
- Consider a consistent display for a positive annual amount whose monthly equivalent rounds below one cent. Preserve the underlying amount.
- Decide whether wages, other income and assets should display more than two decimal places when a pasted value contains fractional cents. Preserve existing shared links.
- If someone leaves a wizard step with an invalid monetary entry, consider showing the native validation message first. The current form keeps the last valid amount.
Chromium, Firefox and WebKit each passed the yearly and monthly typing checks. Chromium also submitted a focused monthly field containing 12.345 with Enter and produced 148.14 annually. The invalid-rent regression covers switching units and then correcting the amount.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 PolicyEngine/cliff-watch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PolicyEngine/cliff-watch#55 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
PolicyEngine/cliff-watch#59 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PolicyEngine/cliff-watch#58 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/cliff-watch#56 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
PolicyEngine/cliff-watch#33 ·
Maintainers usually reply within 2 days
All issues in PolicyEngine/cliff-watch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
product-os/flowzone#2048 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hugomrdias/playwright-test#786 · 1 comment ·
Maintainers usually reply within 1 day
-
code-review secondshift
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
piotrekno1/second-shift#419 ·
Maintainers usually reply within 1 day
-
area:compiler effort:S impact:low platform:wasm type:chore
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
New style: solarpunkOpengood first issue new style
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
musicalbee/design-ontology#112 ·
Maintainers usually reply within 1 day