Fix locale-dependent number formatting on the pricing page
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- next.js, typescript
Research direction
Find the pricing page and locate formatting for prices, limits, and tier values. Check how those values are rendered on the server and client, then use the same explicit locale consistently. Done when pricing values render consistently and the hydration mismatch is resolved.
Written by the indexing model from the issue text.
Description
Pricing values currently use the browser’s default locale. That can make the server-rendered numbers differ from the client-
rendered numbers for some visitors, causing a hydration mismatch. Use one explicit locale consistently for prices, limits,
and tier values.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 227
- Avg merge
- 21h 11m
- Merged PRs (30d)
- 238
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 databuddy-analytics/Databuddy
-
Load docs analytics using Next.js ScriptPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
databuddy-analytics/Databuddy#1147 ·
Maintainers usually reply within 1 day
-
Make the GTM documentation test compatible with Windows line endingsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
databuddy-analytics/Databuddy#1146 ·
Maintainers usually reply within 1 day
-
fix(basket): redact sensitive params and keep query separators in batched outgoing link hrefsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
databuddy-analytics/Databuddy#1143 ·
Maintainers usually reply within 1 day
-
refactor(home): standardize "Install tracking" empty state using EmptyState componentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
databuddy-analytics/Databuddy#1138 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
databuddy-analytics/Databuddy#1131 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in databuddy-analytics/Databuddy
Similar issues
-
native
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
prime-radiant-inc/evener#4839 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
processone/fluux-messenger#1790 ·
Maintainers usually reply within 1 day
-
🛣️ Infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opencrvs/opencrvs-core#14232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kunchenguid/gh-axi#220 ·
Maintainers usually reply within 1 day