gray-mueller / gray-mueller/milk-delivery-app-react
Rider not receiving orders when switching status from "Unavailable" to "Available" during the unassigned order period.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When a rider switches their status from "Unavailable" to "Available" during the time window in which an order has not yet been assigned to any other rider, the system fails to assign the order to the rider. This behavior creates a situation where the rider misses out on receiving available orders even though they are now available to take them.
To Reproduce
A rider is in "Unavailable" status.
An order is placed in the system but has not yet been assigned to any rider.
The rider switches their status to "Available."
The rider does not receive the order, despite the order still being unassigned.
Expected behavior
When a rider changes their status from "Unavailable" to "Available," they should immediately be eligible to receive any unassigned orders. If there is an unassigned order available during this transition, the system should assign it to the rider.
Actual Result
The rider remains unassigned to the order, and no notification or assignment occurs for that order, even though it was unassigned and the rider is available.
Smartphone (please complete the following information):
Device: iPhone15pro
OS: iOS17.6.1
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.
Research direction
Start by reproducing the rider status transition while an order remains unassigned, then trace the status-change and order-assignment flow. Confirm how availability changes are handled and verify that an available rider receives an eligible unassigned order immediately after switching from Unavailable to Available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100