[BUG] Incorrect 'Add your first peak' text when peaks exist
@GalaktusSK is already working on this.
Since Oct 6, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react-native, typescript
- Domain
- internationalization
Research direction
Find the i18n translation files and locate the translations for “Add your first peak.” Update the text to the equivalent of “Add a new peak” in every supported language, keeping “new” in normal capitalization. Verify that the Peaks page uses the updated translations when adding a peak.
Written by the indexing model from the issue text.
Description
Describe the Bug
On the "Peaks" page, the text "Add your first peak" (e.g., "Aggiungi la tua prima vetta" in Italian) is displayed even when the user has already completed some peaks. In this case, it shouldn't say "first". The text should be updated to "Add a new peak" across all languages to be accurate in all cases.
To Reproduce
Steps to reproduce the behavior:
- Add at least one peak in the app.
- Go to the "Peaks" page.
- Observe the text on the button or section used to add a peak.
- See that it still says "Add your first peak" instead of "Add a new peak".
Expected Behavior
The text should be changed from "Add your first peak" to "Add a new peak" (or its equivalent translation) across all supported languages, so it makes sense regardless of whether the user has already added peaks or not.
Environment:
- OS (e.g., iOS 17, Android 14): Any
- Device (e.g., iPhone 15 Pro, Pixel 8): Any
- App Version (e.g., v1.1.0): Current
Additional Context
The new text should be formatted normally, like "Add a new peak" (without "new" in all caps). This needs to be updated in the i18n translation files for all supported languages.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No 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 GiZano/LevelUp
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·