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

Peer reputation: adopt v1's compact inline format on invoice/detail screens

Open Beginner friendly
#321 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
dart, flutter
Domain
mobile

Research direction

Start by locating PeerReputationCard and the pay-invoice, add-invoice, and trade-detail screens named in the issue; compare the existing order-book reputation row and its reputationTradesLabel/reputationDaysLabel keys. Replace the card layout on those screens with the compact inline presentation, retaining the title and existing labels; leave take_order_screen unchanged. Done when those three screens use the compact row and the maker card remains as-is.

Written by the indexing model from the issue text.

Description

Follow-up to #305, which surfaced the taker reputation using the 3-column card shared with the maker's take-order card. That's functional but bulky on the space-constrained pay/add-invoice screens (competes with the QR / input).

v1 shows it as a single compact line — `★ 4.4 · 4 trades · 64 days` — which matches v2's own order-book reputation row (`reputationTradesLabel`/`reputationDaysLabel`).

Proposal

Replace `PeerReputationCard`'s 3-column layout with a compact inline row on the pay-invoice, add-invoice and trade-detail screens.
Reuse the order-book plural label keys (no new stat labels); keep the "Buyer/Seller reputation" title.
Keep the maker's 3-column card in `take_order_screen` as-is (it has the space).
Optional: show `/ 5` after the rating, as v1 does.

Dominant language
Dart
Stars
11
Forks
9
Avg merge
13h 4m
Merged PRs (30d)
259

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 MostroP2P/app

All issues in MostroP2P/app

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.