Enatega Rider App: Show each transaction request TIME below the transaction amount

Open
#864 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
mobile

Research direction

Start by locating the Enatega Rider App transaction list and the component that renders each transaction amount. Confirm how request timestamps are represented, then verify that each transaction displays its request time directly below the amount in the requested format.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
Currently, the transaction details only display the transaction amount without showing the corresponding request time directly underneath. This can lead to confusion for users who want to quickly verify when each transaction was made without diving deeper into additional details or clicking elsewhere.

Describe the solution you'd like
Each transaction in the list should display the request time (e.g., 03:45 PM or 14:25) immediately below the transaction amount. This enhances the readability and usability of the transaction list, allowing users to quickly correlate amounts with their respective timestamps at a glance.

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

Contributor guide

Open the contributing guide

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 raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.