Commit 4bbba6a
committed
Restore profile review context fields expected by the admin UI
The profile review screen was receiving the backend's `context` payload but
never normalizing it into the `reviewContext` shape used by the panel.
That left several review hints and purchase signals effectively dead even
though the data existed. This change maps the backend fields into the
frontend shape so the review panel renders the context it already receives.
Constraint: The backend returns `context.createdAt` and `purchaseCount`, while the screen expects `reviewContext.userCreatedAt` and `hasPurchased`
Rejected: Add a separate adapter layer later | the current screen already has a single normalization point where the mismatch should be corrected
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep frontend profile-review normalization aligned with backend `context` field names unless the backend is changed to emit `reviewContext` directly
Tested: pnpm build
Not-tested: Live profile-review panel rendering against production data1 parent 7631d91 commit 4bbba6a
1 file changed
Lines changed: 22 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
288 | 288 | | |
289 | 289 | | |
290 | 290 | | |
| 291 | + | |
291 | 292 | | |
292 | 293 | | |
293 | 294 | | |
| |||
316 | 317 | | |
317 | 318 | | |
318 | 319 | | |
| 320 | + | |
| 321 | + | |
| 322 | + | |
| 323 | + | |
| 324 | + | |
| 325 | + | |
| 326 | + | |
| 327 | + | |
| 328 | + | |
| 329 | + | |
| 330 | + | |
| 331 | + | |
| 332 | + | |
| 333 | + | |
| 334 | + | |
| 335 | + | |
| 336 | + | |
| 337 | + | |
| 338 | + | |
| 339 | + | |
| 340 | + | |
319 | 341 | | |
320 | 342 | | |
321 | 343 | | |
| |||
0 commit comments