Keyword Search on Withdraw Request Page Not Filtering by Rider Name
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
- Domain
- frontend
Research direction
No file or test is named. Start by reproducing the search on the admin panel's Withdraw Request page, then trace the keyword-search handling and the fields included in its query. Done means entering an existing rider's name displays the matching withdrawal request while preserving the current search behavior.
Written by the indexing model from the issue text.
Description
Describe the bug
On the Withdraw Request page in the admin panel, the keyword search box does not return any results when a rider’s name is entered. This limits the ability to quickly locate specific withdrawal requests tied to individual riders.
To Reproduce
Steps to reproduce the behavior:
Log in to the admin panel
Navigate to the Withdraw Request page
In the keyword search box, enter a rider's name who has an existing withdrawal request
Observe that no results are returned
Expected behavior
The search box should filter and display results based on the rider’s name input, allowing admins to easily locate relevant withdrawal requests.
Screenshots
Image
Desktop (please complete the following information):
OS: Windows 11
Browser: Chrome
Additional context
This issue affects operational efficiency, especially when managing a large number of rider requests. It may be due to the search query not including rider name as a searchable field.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor 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 lambertf917/ubereats-clone-app-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
All issues in lambertf917/ubereats-clone-app-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100