Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Non-functional Links in Help Section

Open
#144 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
mobile-dev

Research direction

Start by opening the Enatega Multivendor Customer App and navigating to the Help section. Inspect how the product page, documentation, and About Us links are configured and triggered on iOS and Android. Done means each link opens its respective destination successfully.

Written by the indexing model from the issue text.

Description

Describe the bug
Within the Enatega Multivendor Customer App, there is a critical issue in the Help section where links to the product page, documentation, and the "About Us" section are not working as intended.

To Reproduce
Steps to reproduce the behavior:

Open the Enatega Multivendor Customer App.
Navigate to the Help section.
Attempt to click on the links to the product page, documentation, and "About Us."
Expected behavior
Clicking on the links in the Help section should redirect users to the respective product page, documentation, and "About Us" section, providing relevant information and assistance.

Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/152266796/54fb7a35-209e-4e23-a691-2307a6ff8489

Smartphone:

Device: iOS and Android
Additional context
Users are unable to access crucial information and resources through these links, hindering their ability to seek assistance and understand more about the app.

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gray-mueller/full-stack-document-solution

All issues in gray-mueller/full-stack-document-solution

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.