bug: remove already implemented features from "coming soon" section
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
Research direction
Start from the homepage route of the Next.js App Router app (the page rendered at /) and search the source for the literal "Coming soon" heading that the report points at. Remove the entries for Streaks, Goals and Public profile from that list, or hide the whole section if nothing is genuinely still planned. Run the app locally and scroll the homepage to confirm the section no longer advertises already-implemented features.
Written by the indexing model from the issue text.
Description
Current behavior
The "coming soon" section at the bottom of the home page shows Streaks, Goals and Public profile that have already been implemented.
Steps to reproduce
- open the homepage (https://open-source-guru.dev) and scroll down to the "Coming soon" section.
Expected behavior
This section should not list already implemented features. Hide it if no features planned
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 3m
- Merged PRs (30d)
- 16
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 tem-ctrl/open-source-guru
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
tem-ctrl/open-source-guru#28 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
tem-ctrl/open-source-guru#26 ·
Maintainers usually reply within 1 day
-
bug: enable auto-approve ci runs on pull requestPossibly taken @tem-ctrl claimed this today. Openbug Internal
tem-ctrl/open-source-guru#33 · 1 assignee ·
Maintainers usually reply within 1 day
-
bug: replace `<domain>` by actual domain in demo api callPossibly taken @dannyward630 claimed this today. Openbug good first issue
tem-ctrl/open-source-guru#31 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
bug: persist signin/dashboard button on page loadPossibly taken @tem-ctrl claimed this today. Openbug work in progress
tem-ctrl/open-source-guru#29 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in tem-ctrl/open-source-guru
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
TomerAberbach/profiler-md#733 ·
Maintainers usually reply within 1 day
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
brentspine/brents-toasts#143 ·
-
🐛 bug 🗺️ DB Models & Ops
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
LibreChat-AI/LibreChat#17214 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Wavvon/Wavvon-clients#136 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
umami-software/umami#4637 ·
Maintainers usually reply within 3 days