Repository navigation
Update/api - #43
Update/api#43
Conversation
Regenerate the typed client from the deployed backend — three new
operations, no schema changes — and build this branch's admin work on it.
Dashboard: the admin nav's four entries collapse into one page at /admin
with Phân tích / Tài chính / Khiếu nại / Nhật ký hoạt động tabs. Retired
paths redirect to ?tab=, and only the open panel renders so a tab switch
fires one panel's requests rather than four. Audit logs had a component
but no route or nav entry, so the panel was unreachable until now.
Charts: shared ApexCharts theming in admin/shared/chart-theme.ts, so the
analytics, finance and claims panels follow one look and the Fuse theme
variables rather than repeating ~40 lines of axis options per chart.
Purchase cost: GET /procurement/batches/{id}/overview drives a two-band
area card — revenue above, what the chợ actually cost below, the gap is
the session's margin. Settlement is read off the batch lifecycle, since
the server refuses hand-off until every non-exempt line is settled;
sessions still being shopped are listed with their progress instead of
being counted as an enormous margin.
Also: invoice PDF download for admins and restaurants, and market
session availability wired into the checkout countdown.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A new Báo cáo sự cố tab, second in the dashboard's bar — before both money tabs, since a shortage at the chợ or at the hub is what a claim is about. It carries the two issue streams an admin can read. Procurement exceptions ride along on GET /admin/order-groups, which maps every batch through ProcurementBatchDtoMapper and so already carries each batch's exceptions[]; one request covers the window. Hub discrepancies are per hub, so the board walks the hub list with each read failing on its own, and offers the acknowledge action — until every discrepancy at a hub is signed off the hub cannot dispatch (BR-HUB-2). The other two streams cannot be shown. Restaurants report issues on a delivered order and drivers on a delivery, but IOrderIssueRepository exposes AddAsync and nothing else and the driver's endpoint is the same — write-only, with no query to read them back. The board says so in a footnote rather than pretending its coverage is complete. Claims: the summary tiles and the status donut move to the incident tab, beside the shortages the claims are filed over. What is left is the queue — filter, inspect, decide. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Code Review Could Not Complete
|
| Options | Enabled |
|---|---|
| Bug | ✅ |
| Performance | ✅ |
| Security | ✅ |
| Business Logic | ✅ |
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
No description provided.