Keep the showcase composer noindex during client-side navigation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
Research direction
Start in frontend/src/services/seo.ts and frontend/src/router/index.ts, then reproduce updateSEO with the DOM fixture described in the issue. Trace the client-side route handling and add a focused regression check for the composer, collection, and published detail routes. Done means the composer stays noindex on direct entry and SPA navigation while the other two routes remain indexable.
Written by the indexing model from the issue text.
Description
Problem
At f371314, community-showcase-new is missing from nonIndexableRoutes in frontend/src/services/seo.ts. Calling updateSEO for /community/showcase/new writes index, follow; the server marks the same route noindex.
Scope
Add this composer route to the existing client exclusion policy. Start in frontend/src/services/seo.ts and frontend/src/router/index.ts.
Done
- Direct entry and SPA navigation to the showcase composer retain
noindex. - The showcase collection and published detail remain indexable.
- Add a focused regression check for these three routes.
Reproduction: call updateSEO({name: 'community-showcase-new', path: '/community/showcase/new', params: {}}, 'en', 'community') with a DOM fixture and inspect meta[name=robots]. This was reproduced with the current helper.
Audit baseline: f371314.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 6h 25m
- Merged PRs (30d)
- 18
Getting set up
We have not checked this project's setup files yet. 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 wavefnd/wave-platform
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#139 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#137 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wavefnd/wave-platform#136 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 94/100
wavefnd/wave-platform#135 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
wavefnd/wave-platform#133 ·
Maintainers usually reply within 1 day
All issues in wavefnd/wave-platform
Similar issues
-
area: global bug dx priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
grafana/mcp-grafana#1267 ·
Maintainers usually reply within 1 day
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
coverage-gap good-first-pattern help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
GoogleCloudPlatform/k8s-aibom#114 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
txn2/mcp-data-platform#1984 ·
Maintainers usually reply within 1 day